This API is deprecated. Use the Settings API instead. Look for the Frequent issue detection (builtin:anomaly-detection.frequent-issues
) schema.
Updates the configuration of frequent issue detection.
The request consumes an application/json
payload.
PUT | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/frequentIssueDetection |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/frequentIssueDetection |
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 JSON body of the request, containing parameters of the frequent issue detection configuration
FrequentIssueDetectionConfig
objectParameters of the frequent issue detection. To learn more about it, see Detection of frequent issues in Dynatrace Documentation.
The detection for applications is enabled (true
) or disabled (false
).
The detection for infrastructure is enabled (true
) or disabled (false
).
The detection for services is enabled (true
) or disabled (false
).
ConfigurationMetadata
objectMetadata useful for debugging
Dynatrace version.
A sorted list of the version numbers of the configuration.
A sorted list of version numbers of the configuration.
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{"frequentIssueDetectionApplicationEnabled": true,"frequentIssueDetectionInfrastructureEnabled": true,"frequentIssueDetectionServiceEnabled": true}
Success. 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/frequentIssueDetection/validator |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/frequentIssueDetection/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 applications from the GET request example. It activates frequent issue detection for applications.
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. Be sure to create a backup copy of your current configuration with the GET request.
curl -L -X PUT 'https://mySampleEnv.live.dynatrace.com/api/config/v1/frequentIssueDetection' \-H 'Authorization: Api-Token dt0c01.abc123.abcdefjhij1234567890' \-H 'Content-Type: application/json' \--data-raw '{"frequentIssueDetectionApplicationEnabled": true,"frequentIssueDetectionServiceEnabled": true,"frequentIssueDetectionInfrastructureEnabled": false}'
https://mySampleEnv.live.dynatrace.com/api/config/v1/frequentIssueDetection
{"frequentIssueDetectionApplicationEnabled": true,"frequentIssueDetectionServiceEnabled": true,"frequentIssueDetectionInfrastructureEnabled": false}
204
The updated configuration has the following parameters: