Details Field not showing on Opsgenie Events

[Julian Sarrelli]

Hi everyone,

We have an integration with Opsgenie by using the Java Opsgenie client 

"com.opsgenie.integration" % "sdk"                   % "2.11.2"

In which we create and close events. In these requests, we are sending data in the details field. 
We've detected that these details sometimes display data and sometimes don't, although we always send the same data.  (See Extra Properties)

[Alan Violada · Accepted solution]

Hey Julian, Alan from the Opsgenie Support team here.

In order to display that information on the alert, you are going to want to make sure that in the integration settings, you have mapped a field in the alert details to show the {{extraProperties}} value: 

https://support.atlassian.com/opsgenie/docs/use-advanced-integration-settings/ 

 

Also worth noting, we recently identified and fixed a bug where the extra properties were being displayed on alerts even if they had not been configured in the integration:

https://jira.atlassian.com/browse/OPSGENIE-1867 

This could explain why you were seeing it intermittently, even without changing any settings - Now that this is fixed, however, this does need to be configured in the integration.

Cheers,

Alan

[Julian Sarrelli]

Alan, somewhere along the 12th of February something changed and it stopped displaying the detail fields

This is how we are calling the endpoint using the SDK. 

log.fields("details" -> detailsField.mkString(", ")).info(s"Sending opsgenie ${notificationConfig.action}")

val alertRequest = (new CreateAlertRequest)
  .message(event.title)
  .description(event.summary)
  .source(event.source)
  .priority(ogPriority(event.severity))
  .details((event.details + ("View in Blue Matador" -> event.href)).asJava)
  .alias(event.incidentId.toString)

client.alertV2.createAlert(alertRequest)

In the details parameter, we are sending a map of <String,String>

In this example I see the request is being sent with a bunch of fields but nothing comes up on the Opsgenie UI

And here I have a similar event, with the same payload,  on February 11th

[Alan Violada]

Hey Julian,

That matches what I mentioned - Since the fix release on Feb 12, you now need to manually configure the "extraProperties" value to be displayed in the alert via the integration settings.

So while the payload you are sending might have all the info, you are likely missing the part of configuring it on the integrations "Create Alert" rule.

If you run into issues configuring that, I would recommend creating a support ticket at Atlassian Support so we can provide more detailed assistance.

Cheers,

Alan