Gets the configuration of anomaly detection for database services.
The request produces an application/json
payload.
GET | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/anomalyDetection/databaseServices |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/anomalyDetection/databaseServices |
To execute this request, you need an access token with ReadConfig
scope.
To learn how to obtain and use it, see Tokens and authentication.
The request doesn't provide any configurable parameters.
DatabaseAnomalyDetectionConfig
objectThe configuration of the anomaly detection for database services.
Parameters of the failed database connections detection.
The alert is triggered when failed connections number exceeds connectionFailsCount during any timePeriodMinutes minutes period.
Configuration of failure rate increase detection.
Configuration of response time degradation detection.
DatabaseConnectionFailureDetectionConfig
objectParameters of the failed database connections detection.
The alert is triggered when failed connections number exceeds connectionFailsCount during any timePeriodMinutes minutes period.
Number of failed database connections during any timePeriodMinutes minutes period to trigger an alert.
The detection is enabled (true
) or disabled (false
).
The X minutes time period during which the connectionFailsCount is evaluated.
FailureRateIncreaseDetectionConfig
objectConfiguration of failure rate increase detection.
Parameters of failure rate increase auto-detection. Required if detectionMode is DETECT_AUTOMATICALLY
. Not applicable otherwise.
The absolute and relative thresholds both must exceed to trigger an alert.
Example: If the expected error rate is 1.5%, and you set an absolute increase of 1%, and a relative increase of 50%, the thresholds will be: Absolute: 1.5% + 1% = 2.5% Relative: 1.5% + 1.5% * 50% = 2.25%
How to detect failure rate increase: automatically, or based on fixed thresholds, or do not detect.
DETECT_AUTOMATICALLY
DETECT_USING_FIXED_THRESHOLDS
DONT_DETECT
Fixed thresholds for failure rate increase detection.
Required if detectionMode is DETECT_USING_FIXED_THRESHOLDS
. Not applicable otherwise.
FailureRateIncreaseAutodetectionConfig
objectParameters of failure rate increase auto-detection. Required if detectionMode is DETECT_AUTOMATICALLY
. Not applicable otherwise.
The absolute and relative thresholds both must exceed to trigger an alert.
Example: If the expected error rate is 1.5%, and you set an absolute increase of 1%, and a relative increase of 50%, the thresholds will be: Absolute: 1.5% + 1% = 2.5% Relative: 1.5% + 1.5% * 50% = 2.25%
Absolute increase of failing service calls to trigger an alert, %.
Relative increase of failing service calls to trigger an alert, %.
FailureRateIncreaseThresholdConfig
objectFixed thresholds for failure rate increase detection.
Required if detectionMode is DETECT_USING_FIXED_THRESHOLDS
. Not applicable otherwise.
Sensitivity of the threshold.
With low
sensitivity, high statistical confidence is used. Brief violations (for example, due to a surge in load) won't trigger alerts.
With high
sensitivity, no statistical confidence is used. Each violation triggers alert.
HIGH
LOW
MEDIUM
Failure rate during any 5-minute period to trigger an alert, %.
LoadDropDetectionConfig
objectThe configuration of load drops detection.
The detection is enabled (true
) or disabled (false
).
Alert if the observed load is less than X % of the expected value.
Alert if the service stays in abnormal state for at least X minutes.
LoadSpikeDetectionConfig
objectThe configuration of load spikes detection.
The detection is enabled (true
) or disabled (false
).
Alert if the observed load is more than X % of the expected value.
Alert if the service stays in abnormal state for at least X minutes.
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.
ResponseTimeDegradationDetectionConfig
objectConfiguration of response time degradation detection.
Parameters of the response time degradation auto-detection. Required if the detectionMode is DETECT_AUTOMATICALLY
. Not applicable otherwise.
Violation of any criterion triggers an alert.
How to detect response time degradation: automatically, or based on fixed thresholds, or do not detect.
DETECT_AUTOMATICALLY
DETECT_USING_FIXED_THRESHOLDS
DONT_DETECT
Fixed thresholds for response time degradation detection.
Required if detectionMode is DETECT_USING_FIXED_THRESHOLDS
. Not applicable otherwise.
ResponseTimeDegradationAutodetectionConfig
objectParameters of the response time degradation auto-detection. Required if the detectionMode is DETECT_AUTOMATICALLY
. Not applicable otherwise.
Violation of any criterion triggers an alert.
Minimal service load to detect response time degradation.
Response time degradation of services with smaller load won't trigger alerts.
FIFTEEN_REQUESTS_PER_MINUTE
FIVE_REQUESTS_PER_MINUTE
ONE_REQUEST_PER_MINUTE
TEN_REQUESTS_PER_MINUTE
Alert if the response time degrades beyond X milliseconds.
Alert if the response time degrades beyond X %.
Alert if the response time of the slowest 10% degrades beyond X milliseconds.
Alert if the response time of the slowest 10% degrades beyond X %.
ResponseTimeDegradationThresholdConfig
objectFixed thresholds for response time degradation detection.
Required if detectionMode is DETECT_USING_FIXED_THRESHOLDS
. Not applicable otherwise.
Minimal service load to detect response time degradation.
Response time degradation of services with smaller load won't trigger alerts.
FIFTEEN_REQUESTS_PER_MINUTE
FIVE_REQUESTS_PER_MINUTE
ONE_REQUEST_PER_MINUTE
TEN_REQUESTS_PER_MINUTE
Response time during any 5-minute period to trigger an alert, in milliseconds.
Sensitivity of the threshold.
With low
sensitivity, high statistical confidence is used. Brief violations (for example, due to a surge in load) won't trigger alerts.
With high
sensitivity, no statistical confidence is used. Each violation triggers an alert.
HIGH
LOW
MEDIUM
Response time of the 10% slowest during any 5-minute period to trigger an alert, in milliseconds.
{"databaseConnectionFailureCount": {"connectionFailsCount": 5,"enabled": "true","timePeriodMinutes": 5},"failureRateIncrease": {"detectionMode": "DETECT_USING_FIXED_THRESHOLDS","thresholds": {"sensitivity": "LOW","threshold": 10}},"loadDrop": {"enabled": true,"loadDropPercent": 40,"minAbnormalStateDurationInMinutes": 5},"loadSpike": {"enabled": false},"responseTimeDegradation": {"automaticDetection": {"loadThreshold": "ONE_REQUEST_PER_MINUTE","responseTimeDegradationMilliseconds": 250,"responseTimeDegradationPercent": 90,"slowestResponseTimeDegradationMilliseconds": 500,"slowestResponseTimeDegradationPercent": 200},"detectionMode": "DETECT_AUTOMATICALLY"}}
In this example, the request lists the current configuration of anomaly detection for database services.
The API token is passed in the Authorization header.
The configuration has the following settings:
curl -X GET \https://mySampleEnv.live.dynatrace.com/api/config/v1/anomalyDetection/databaseServices \-H 'Authorization: Api-Token dt0c01.abc123.abcdefjhij1234567890'
https://mySampleEnv.live.dynatrace.com/api/config/v1/anomalyDetection/databaseServices
{"metadata": {"clusterVersion": "1.163.2.20190201-072431","configurationVersions": [3]},"responseTimeDegradation": {"detectionMode": "DONT_DETECT"},"failureRateIncrease": {"detectionMode": "DETECT_USING_FIXED_THRESHOLDS","thresholds": {"threshold": 0,"sensitivity": "LOW"}},"databaseConnectionFailureCount": {"enabled": true,"connectionFailsCount": 5,"timePeriodMinutes": 5}}
200