Nick Haller Atlassian Team

Hi @Carol Saldanha , If you are parsing the entire {{_payload}} to the description field, and custom fields from the request form in the alert e.g email address and contact number are not shown, then I'd assume they are not sending from Jira / JSM to Opsgenie. Are you not seeing these fields at all in the Opsgenie alert?…

Hi @Randy Everett , You can have Opsgenie alerts create Jira tickets with both types of Jira integrations. With our Legacy integration, this other Community article should help with getting things configured within Opsgenie. You can edit the filter of the "For other Opsgenie alerts" section to only have certain alerts…

Hi Everyone, We now have a public feature request that you all can follow, watch and vote for here: https://jira.atlassian.com/browse/OPSGENIE-243

Hi @William Lee , That unfortunately is not possible at this time, but we have an open feature request you can follow, watch and vote for here: https://jira.atlassian.com/browse/OPSGENIE-471 Like you mentioned, closest functionality Opsgenie has at this time is with a notification policy that delays / suppresses…

Hi @rowen , If you are using an API key from an API integration that is assigned to the Watcher Test team, you realistically do not need to even specify the responders in request - since it will automatically send to the team the integration is assigned to. This leads me to believe that there is some workflow configured in…

Hi @Afonso Henrique Rodrigues Alves , I think there is confusion with the terminology being used. You're saying the alerts are duplicating, meaning a new alert is being created for each email. When it seems like you want these to deduplicate, or increase in count under one alert. In that case, you are correct that the…

Hi @Afonso Henrique Rodrigues Alves , If you want all emails to create alerts vs. deduplicating, you don't necessarily need to configure anything in the alias field. Leaving it blank would automatically parse the alert's ID into the alias. You could consider having the create alert action only trigger for certain types of…

Hi @Lee Beenen , You could leverage our backup tool to grab all configurations, and then clone them in the new Opsgenie instance later: https://github.com/opsgenie/opsgenie-configuration-backup But it cannot backup alerts, or the integrations' API keys. Since the integrations are essentially being cloned, they'd all have…

Hi @Rosa M Fossi , It seems like you'd want to configure a workflow that manages after hours alerts, and this would entail adding another rotation that also manages on-call after hours. This might be a duplicate of the present on-call rotation with different hours / same users - but in a different order offset by one user.…

It looks like the resources field parses a bracket which is a different formatting than the reasons field: So the resources field might be something like: {{_payload.resources}} {{_payload.substringBetween("\"resources\":[\"","\"]")}}

Hi @pushpa , Not entirely sure why the Subject field is included as a default field parsing in the payload, since it's not included as one in the CloudWatch Events integration: Which is why I assume it's sending as null. It is a default field in the other CloudWatch integration, so maybe that's the reason. As for…

Hi @Paweł Grams , There are some extra fields not included with the Email integration by default, but specifically parse in the headers of the payload - including the date: Since it's nested under the headers, you could use something like this to extract it into the alert: {{_headers.DATE}} As well use some form of string…

I don't believe there is unfortunately.

Hi @shlomo.neiman , An Email integration can only have one address per integration at this time. Depending on your plan (Standard and Enterprise), you can configure multiple create alert actions under the integration's Advanced tab that manage alert fields depending on - for example - if the from address is a certain…

Hi @shlomo.neiman , Opsgenie does have rate limiting, but it's dependent on your user count: https://docs.opsgenie.com/docs/api-rate-limiting 10 emails simultaneously shouldn't be an issue, but 100 might be.

Hi @Josiah Tillett , I believe the user would need to be removed from within Opsgenie even if they were removed from your SSO. And I believe they would remain active as well even if removed from SSO. A user cannot be removed / deleted from Opsgenie until they are removed from any schedules and/or escalations they are…

Yeah seems like you'd want a website monitoring tool such as Pingdom, Uptime Robot, etc. But just to be clear, the heartbeart would be a ping sent from your external system to Opsgenie, not Opsgenie reaching out to the external system. So if your website can send some sort of job to Opsgenie, and it's not received over the…

Hi @joana , If you are triggering Opsgenie alerts through a Jira webhook, seems like you could configure some sort of JQL that triggers once the field(s) is populated. Might look something like this:

Yes, the idea would be the same for Jira as it is for JSM. As for the latter - seems like when the Jira issues are updated, you want those reflected on the Opsgenie alert (or vice versa)? That unfortunately isn't really possible at this time.

Hi @rogierl , Closest thing Opsgenie has to that use case is Heartbeats. These essentially act like a dead man's switch, and can monitor that periodic tasks are running as expected. Say for example you schedule a heartbeat to receive a ping from your external system every 12 hours. If Opsgenie does not receive that ping…

Hi @mischlerpa , Like mentioned above, can you check whether or not the alert / test is being sent through the Default API? Again - Opsgenie handles some test alerts so the connection can be tested with the actual integration processing taken out of the equation, but ensures there is a connection with Opsgenie.

That works too! You can realistically filter on any alert field in the Notification policy. 

That's a great catch @Karthikeyan Mahadevan !

Hi @mischlerpa , Some integrations / test alerts trigger through the account's Default API. Not sure if Dynatrace is one of them, but this is how Opsgenie handles some test alerts so the connection can be tested with the actual integration processing taken out of the equation, but ensures there is a connection with…

Hi @Allen Oliver . We'll provide an in-app announcement if any numbers are added or removed to the vCard. We haven't had any updates to them in a while, but this is an example of one from a few years ago:

Hi @Vitalii Bendyna , That is not possible at this time. Typically best practice is having a Slack integration / channel per team. Obviously that does not always meet each use case, but the idea would be to have each member of a team also be a member in the Slack channel:

Hi @Pedro Parellada , That's the current workflow with Opsgenie incidents. Say for example an incident is created automatically through an incident rule, and the incident rule is tied to a service: The service adds multiple responders to the incident at creation: The alert that initially created the incident would become…

Hi @Doug McGibbon , Depending on your plan* you could configure multiple create alert actions to manage creating alerts per client. This can be configured under the Advanced tab of the integration. Along with configuring each action, add a tag to each action that identifies the client. For example: Then when you need…

Hi @Alain Rohner , Seems like you are aware notes can be added at alert creation through the Create Alert action's Note field. But it's important to note the Add Note action would be a second request received by Opsgenie, and does not apply at alert creation. For example below, I have a Create Alert action that adds a note…

Hi @Sreenatha Reddy J , I've moved this question to the Jira queue as I believe it relates more to that product vs. Statuspage - which this was initially opened in. Let me know if that's not the case.