alertmanager

Describe the bug

Right now the deployment yaml (from the helm chart) has the same liveness and readiness probe:

          readinessProbe:
            httpGet:
              path: /config
              port: http
            initialDelaySeconds: 1
            periodSeconds: 3
          livenessProbe:
            httpGet:
              path: /config
              port: ht

Thank you for your hard work and great project!

Unfortunately we have found an issue in 1.0.

In our case, when the JiraAlert is triggered by the Alertmanager, it creates new Jira defect, without adding additional Label. For example if the service is down Jira Alert uses the label like: ALERT{alertname="ServiceDown",namespace="",service_name=""} which should already be added to Defect.

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Checked that your issue isn't already filled: https