Updates the configuration of anomaly detection for the specified process group.
The request consumes an application/json
payload.
PUT | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/anomalyDetection/processGroups/{id} |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/anomalyDetection/processGroups/{id} |
To execute this request, you need an access token with WriteConfig
scope.
To learn how to obtain and use it, see Tokens and authentication.
The Dynatrace entity ID of the required process group.
The JSON body of the request. Contains parameters of anomaly detection for a process group.
AnomalyDetectionPG
objectConfiguration of anomaly detection for the process group.
Configuration of the availability monitoring for the process group.
AvailabilityMonitoringPG
objectConfiguration of the availability monitoring for the process group.
How to monitor the availability of the process group:
PROCESS_IMPACT
: Alert if any process of the group becomes unavailable.MINIMUM_THRESHOLD
: Alert if the number of active processes in the group falls below the specified threshold.OFF
: Availability monitoring is disabled.MINIMUM_THRESHOLD
OFF
PROCESS_IMPACT
Alert if the number of active processes in the group is lower than this value.
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{"availabilityMonitoring": {"method": "MINIMUM_THRESHOLD","minimumThreshold": 5}}
Success. The configuration has been updated. Response doesn't have a body.
We recommend that you validate the payload before submitting it with an actual request. A response code of 204 indicates a valid payload.
The request consumes an application/json
payload.
POST | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/anomalyDetection/processGroups/{id}/validator |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/anomalyDetection/processGroups/{id}/validator |
To execute this request, you need an access token with WriteConfig
scope.
To learn how to obtain and use it, see Tokens and authentication.
Validated. The submitted configuration is valid. Response doesn't have a body.
In this example, the request updates the configuration of anomaly detection for the process group with the ID of PROCESS_GROUP-52B42D0616D556F5 from the GET request example. It changes the method of detection to PROCESS_IMPACT.
The API token is passed in the Authorization header.
You can download or copy the example request body to try it out on your own. First, be sure to create a backup copy of your current configuration with the GET process group anomaly detection configuration call.
curl -L -X PUT 'https://mySampleEnv.live.dynatrace.com/api/config/v1/anomalyDetection/processGroups/PROCESS_GROUP-52B42D0616D556F5' \-H 'Authorization: Api-Token dt0c01.abc123.abcdefjhij1234567890' \-H 'Content-Type: application/json' \--data-raw '{"availabilityMonitoring": {"method": "PROCESS_IMPACT"}}'
https://mySampleEnv.live.dynatrace.com/api/config/v1/anomalyDetection/processGroups/PROCESS_GROUP-52B42D0616D556F5
{"availabilityMonitoring": {"method": "PROCESS_IMPACT"}}
204