How the fields mapping works between Dynatrace and Opsgenie

[serge calderara]

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 :

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 ?

Regards

[connor mcguane]

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?

[serge calderara]

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 ?

regarsd

[connor mcguane]

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.

[serge calderara]

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

regards

[connor mcguane]

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

[serge calderara]

@connor mcguane , here is