How to extract specific key/value in a problem detail and display it in cutomised email Body

Platform Alerting
, ,
1

Hi Dynatrace Community,

I have created an SLO that triggers custom alerts

When the event occurs it generates a problem that I can query using API V2 with bellow details :

Is there a possibility that I can extract any of the key/values in problem details and display it in custom email body and send notification ?

In my situation I need to extract  “key”: “dt.davis.analysis_time_budget” and display it in email body.
The builting placeholders do not allow me to solve this situation.

Thank you in advance.
Best Regards
Farid

<span class="">"data"</span><span>: {</span>          <span class="">"eventId"</span><span>: </span><span>"5613985181028457511_1707653400000"</span><span>,</span>          <span class="">"startTime"</span><span>: </span><span>1707653400000</span><span>,</span>          <span class="">"endTime"</span><span>: </span><span>1707658440000</span><span>,</span>          <span class="">"eventType"</span><span>: </span><span>"CUSTOM_ALERT"</span><span>,</span>          <span class="">"title"</span><span>: </span><span>"slo_dtd_inactivity"</span><span>,</span>          <span class="">"entityId"</span><span>: {</span>            <span class="">"entityId"</span><span>: {</span>              <span class="">"id"</span><span>: </span><span>"SERVICE_METHOD-E490FAD90B5A25FE"</span><span>,</span>              <span class="">"type"</span><span>: </span><span>"SERVICE_METHOD"</span>
            },
            <span class="">"name"</span><span>: </span><span>"migrate"</span>
          },
          <span class="">"properties"</span><span>: [</span>            {
              <span class="">"key"</span><span>: </span><span>"dt.davis.analysis_time_budget"</span><span>,</span>              <span class="">"value"</span><span>: </span><span>"0"</span>
            },
            {
              <span class="">"key"</span><span>: </span><span>"dt.davis.analysis_trigger_delay"</span><span>,</span>              <span class="">"value"</span><span>: </span><span>"3600"</span>
            },
            {
              <span class="">"key"</span><span>: </span><span>"dt.event.allow_davis_merge"</span><span>,</span>              <span class="">"value"</span><span>: </span><span>"false"</span>
            },
            {
              <span class="">"key"</span><span>: </span><span>"dt.event.allow_frequent_issue_detection"</span><span>,</span>              <span class="">"value"</span><span>: </span><span>"false"</span>
            },

            {
              <span class="">"key"</span><span>: </span><span>"dt.event.disable_davis_merge_reason"</span><span>,</span>              <span class="">"value"</span><span>: </span><span>"Set by event reporter"</span>
            },
            {
              <span class="">"key"</span><span>: </span><span>"dt.event.group_label"</span><span>,</span>              <span class="">"value"</span><span>: </span><span>"Custom alert"</span>
            },
            {
              <span class="">"key"</span><span>: </span><span>"dt.event.impact_level"</span><span>,</span>              <span class="">"value"</span><span>: </span><span>"Services"</span>
            },
            {
              <span class="">"key"</span><span>: </span><span>"dt.event.is_rootcause_relevant"</span><span>,</span>              <span class="">"value"</span><span>: </span><span>"true"</span>
            },
            {
              <span class="">"key"</span><span>: </span><span>"dt.event.metric_selector"</span><span>,</span>              <span class="">"value"</span><span>: </span><span>"(func:slo.slo_dtd_inactivity_migration_postpaid_prepaid):filter(eq(\"dt.entity.service_method\",SERVICE_METHOD-E490FAD90B5A25FE))"</span>
            },
            {
              <span class="">"key"</span><span>: </span><span>"dt.event.metric_threshold"</span><span>,</span>              <span class="">"value"</span><span>: </span><span>"8.0"</span>
2

I would say Workflows is the answer for this specific scenario.

You can start with a problem trigger

From here you can extract whatever information you need a use the new MS365 integration

3

Thank you PacoPorro for your answer, I will explore the scenarios you provided and keep you updated.

Best Regards

Farid