15 Apr 2024
09:08 PM
- last edited on
08 Aug 2024
02:48 PM
by
Michal_Gebacki
If one wants to create a Problem in Dynatrace, we can create an event of type "CUSTOM_ALERT", which will make it's way into a Problem.
When creating this event, one gets back correlationId's, but not the ID of the corresponding problem.
What are the best practices for getting the problem ID after a "CUSTOM_ALERT" event creation?
29 Apr 2024 09:51 AM
For me running /api/v2/events with eventSelector equals to the correlationId is working OK.
HTH
Yos
01 May 2024 11:36 PM
I tried it out, but I only get the event detail.
What I'm trying to find out is the problem Id.
I need this to close the corresponding Problem that is opened, based on the event.
Best strategy I have found out is searching problems by the title of the event, through the "text" scope in problemSelector. Besides the obvious problem of what to search exactly, the text search only supports 30 characters...
There should be a way to search problems that contain a certain event... The information of the correlationId is in the event, which is in the problem data, but it seems that it is not searchable?
02 May 2024 06:40 AM
Stand corrected !
Yes, you are right , only the search via text can help here - very odd ! 😞
Yos
13 Mar 2025 02:49 PM
ugh...i was finally getting around to similar. Trying to build a bi-directional integration with LogicMonitor and Dynatrace. I guess another instance where Dynatrace falls short again.
I agree Antonio.....any Problem created from an Event should have a list of related CorrelationIDs as an attribute. Then an API call to Problems API with the CorrelationID should allow the associated problem to be closed. With options like, explicit match so that one doesn't accidently close a problem where multiple correlationIDs are related but not all solved.
Dynatrace, if you see this, think about it. and ,No, I'm not creating a enhancement proposal.