cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Extracting anomaly detection setting for each service

pshinde2
Inactive

Hi , We have made threshold changes for response time and failure rate alerting for various services since the time of deployment. Now we wanted to override those custom settings with global default values . Problem here is that the services which are using custom/fixed values did not take global defined values and we did not kept the track of those when we made threshold changes to various services individually . Is their any way or any API call available to pull the details which will show if service is using global threshold values or custom values. This details will us to make required changes to all those services to use global values instead of fixed values.


5 REPLIES 5

Unfortunately anomaly detection API is only for global settings, not for those related to particular entities.

Sebastian

Julius_Loman
Leader
It's not in the Config API yet. If you know your service entity IDs, it's possible to emulate requests from UI and call the same rest API requests the UI is calling. It's nasty, unsupported, may change between Dynatrace updates, but it's the only way to automate it until the anomaly detection is part of config API.

wolfgang_beer
Dynatrace Champion
Dynatrace Champion
A simple workaround would be to define a custom event on a selected service or service method with a threshold and use its customMetricEvent API endpoint to update that config.

Custom event configs are fully configurable on instance level as well as on group level and available through the API.

Best greetings,

Wolfgang


Hi Wolfgang ,

Thanks , Currently our concern is to figure out which all services using custom/fixed values as threshold . We don't have exact record of service which are using those custom thresholds. It would be great if Dynatrace provide some solution around it . Atleast list of services using Global values and list of services not using global anomaly settings.

@Wolfgang B. Any idea when the anomaly detection API endpoints will be available at the service level?