Integration > Dynatrace(DT) > events load: to-include associated ticket (DT# P-)info

AS-IS:

======

Integration > dynatrace > event load > post-load event: incident & alerts page > no dynatrace P- info found, P- is dynatrace side ticket# info.

Note: current cloudpak seems to grab the events from {dynatrace-SAAS-instance}/api/v2/events, or, /api/v2/events/eventid, which returns only event number but without associated P- info.

Desired TO-BE:

========================

post-load event (incident & alerts) page could include dynatrace P- info (or say, data source system ticket# info, at least ticket ID).

Note:

In order to grab P- info, usually we need to use below API

{dynatrace-SAAS-instance}/api/v2/problems, or,api/v2/problems/problemid has BOTH event and problem info.

In dynatrace, DavisAI will auto-bundle 1-n relevant events into 1 problem, so 1 problem json could include multi eventids and their details.

e.g.

"displayId": "P-2410515755" and matching "eventId"(s).

{ "problemId": "6422462280983342200_1728759480823V2",

"displayId": "P-2410515755",...

}

{... "eventId": "eventid1", ...}

{... "eventId": "eventid2", ...}

Therefore FYI potential one solution (TBD by IBM expertise):

data model1 (pre-existing): eventid ~ CI/resource (integration with /api/v2/events, or, /api/v2/events/eventid)

data model2 (new): problemid ~ eventid (integration with dynatrace api/v2/problems & api/v2/problems/problemid)

then join

Business impact:

========================

This will be critical for cross-reference during multi-stakeholders, especially whom are using both data-source system as well as IBMAIOps system.

If feasible, kindly arrange to near-term upcoming release.

Annex:

========================

Detail samples please refer to IBM case T# listed in "Additional details".