Hi,
Using above with the from and to, returns an empty list. I assume using the EPOC time as parameter format is fine, but does this work without the extra eventType and or eventId parameters?
So is my assumption good that you can collect events from a past period?
KR Henk
Solved! Go to Solution.
You have to use timestamps for from and to. I will add that info in help docu, thanks for the hint. Yes the endpoint allows you to fetch events on a environment global level as well as on entity level by using the entityId= filter. eventType filter is also possible.
Of course you can fetch events from the past, thats the purpose of the endpoint.
i am getting this below error for the Problem API URL for my tenent :
https://aabbcc.live.dynatrace.com/api/v1/problem/feed
{"error":{"code":401,"message":"Unsupported authentication mechanism -> 'Basic', could not be used as fallback."}}
Did you create and use a Dynatrace API token? You have to add the Api-Token either as HTTP GET parameter or as a HTTP Header field:
?Api-Token=<YOUR_TOKEN>
See the help docu here:
https://www.dynatrace.com/support/help/dynatrace-api/authentication/how-do-i-set-up-authentication-to-use-the-api/
Hi Wolfgang,
eventType or entityId, both work perfect, if you use from and to you get unexpected results?
Correct?
KR Henk
What do you mean with unexpected results? The expected result is to get all events that are within that selected timeframe.
Hi Wolfgang,
No sorry, that's what I expected but no. Using a short period in the past returns 0, and when using a long period he only show's a few "resent" events. Shall I create a ticket or do you have any extra advise for me?
KR Henk
I will create a ticket for that. Thanks for reporting. Can you please also post a screenshot of the event types you see in the same timeframe within the WebUI? The reason is very likely an event type R&D forgot to export.
Thanks,
Wolfgang
I meant 'event types' within the individual host or process screens. See below:
I see that we do not expose the process restart event as we will deprecate that event type in the future. If you have lots of those event types the overall number is wrong. We will fix that.