Regarding the raised concerns:
- Having admin permissions or at least permission to change monitoring settings.
- Using the problems Api v2 under environment API V2.
- Create authentication token with "problems.read && optionally you can add problems.write".
- Use the generated token to unlock the Api and fetch the related problems details.
Connectivity between Dynatrace and API endpoint or Postman should be conducted properly even through proxy , it won't be an issue as long as the communication is stable.
The attached URL will guide you to accomplish the objective:
As simple as that specify the below attached parameters.
For Sorting:
Tip:
- Form : will be 2H and to will be now "Not vice versa" 😉 😊
Hoping it helps.
KR,
Peter.
Regarding the metrics point, it can be exposed under Observe and explore:
- Data Explorer
- Metrics
You can customize the preferred visualizations through dashboard or creating a metric events for alerting as per monitoring requirements.
- https://docs.dynatrace.com/docs/analyze-explore-automate/metrics-classic
- https://docs.dynatrace.com/docs/discover-dynatrace/platform/davis-ai/anomaly-detection/set-up-a-cust...
- https://docs.dynatrace.com/docs/analyze-explore-automate/dashboards-and-notebooks/dashboards-new
Hoping it adds value.
BR,
Peter
thank you all, we are using Postman and when using the table visualization it shows just 10 problems from a total of 15 problems, how can we see the total amount of problems ? is like the table trim the data.
here is the total count
and the total of problems on postman page
Hi.
So, in general, if pagination occurs, you'd do further calls as needed, using only the querying parameter nextPageKey with the value shown in the last call
About giving you only the first 10: as it is shown in the screenshot, either it is what was asked for in pageSize, or it is a default.
Kind regards,
Paulo.
Featured Posts
