Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How the fields mapping works between Dynatrace and Opsgenie

Dear all,

We have some issue while trying to mapp different fields from Dynatrace payload to Opsgenie.

Based on the documentation, there is a custom pay load define as below :


image (3).png

For exemple in opsgenie some available fields are named as  :

  • Problem_Id
  • State
  • problem_severity
  • problem_url

Does it means that in Dynatrace payload the naming should match same name ?

Actually only ProblemId , State, ProblemDetailJson is able to be mapped corrrectly by opsgenie.

The sample dynatrace payload is as below


As you can see for exemple, the problem_url is present in payload with same name as in opsgenie default field, BUT it cannot be mapped ( confirm in logs)


Could you help me clarifiy what is the rule on fields naming inside dynatrace in order to get the field mapping working correctly and why some mapped some others not even with same name ?


1 answer

I assume you mean mapping in the Dynatrace integration in Opsgenie.  For example, your issue is putting the {{problem_url}} in the Description field of the alerts.  Problem URL is not being populated in the alerts?


Also, in Dynatrace, how are you sending the alert, via a Custom Integration or the Opsgenie integration.


Finally, is that screenshot from the Opsgenie logs?

Hello @connor mcguane , yes the screen shot is from the Osgeneni Log.

We try to understand what is the naming correspondance need to be done in order that field maping in opsgenie works

What I mean by field mapping in opsgeni is that opgenie is capable to populate incoming field to correct place holder of the integration.

As you can see in capture, the problem URL contains something but when I display the Problem_URL of the intergration in an Alert field, the field is null.

Any idea ?


what I find interesting is when I look in my Opsgenie logs for an incoming Dynatrace alert, the information is all under _incoming_data: _parsed_data.  Not _payload: like in your example.

In my case, we are putting that field into Extra properties key-value pair.

2021-06-04 08_48_01-Opsgenie - Integration.png

Hello @connor mcguane ,

Sorry I miss explain :

In the log incoming raw data from Dynatrace I can see them in 

[DynatraceV2] Received integration request

Data processd by opgenie I can see them under Processed incomingData



If you open any of this entry, you will see there is a payload section you can expand, this is the section I screen shot where you can see incoming fields and mapped field in the 2 sections

This is what I have done, place all the field under extra property and all are null except STATE and Problem ID, and I do not know why.

Note : We are using the Dynatrace Web Hook integration


Can you post a screenshot of your Integration in Opsgenie for Dynatrace.  Thanks

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Opsgenie

Leveraging Atlassian’s Opsgenie and AWS Cloudformation Registry to stay ahead of incidents

In the past, managing IT infrastructure was a hard job. It required a lot of manual effort and it was hard to keep track of all the necessary information (monitoring, scalability etc). Thankfully, as...

2,440 views 0 13
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you