- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
To reduce alert fatigue, Synthetic tests can be retried when a test run fails. If you have configured a test to be retried on failures, this is a fast retry.
With a fast retry, Datadog runs a Synthetic test multiple times before transitioning the test’s monitor to alert and sending you a notification. For more information about monitors associated with your Synthetic tests, see Use Synthetic Test Monitors.
While fast retry results are used in the local group evaluation, only the final retry is taken into account in the total group evaluation. The original run and all intermediate retries are discarded from the evaluation.
A run that is still failing after it has reached the maximum number of retries is considered final, and this final result is taken into account in the total group evaluation.
In this example, a Synthetic test is scheduled to run every three minutes, and has a retry configured to a maximum of two times with a delay of two minutes.
The evaluation only takes the final retry into account for the total group evaluation.
When all retries fail:
Or when a retry is successful:
Note: Depending on what you set for the minFailureDuration
and minLocationsFailed
parameters, you may see different behavior.
The system populates the timestamp for a final result with the time when the test was retried, not the time the test was originally scheduled. Results are considered at the timestamp when the test was started. Due to the test’s execution time, there may be a small delay before the results become available for the evaluation.