- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Sentry provides self-hosted and cloud-based application performance monitoring and error tracking that helps software teams see clearer, solve quicker, and learn continuously.
The Datadog Sentry integration automatically forwards Sentry events to the Datadog event stream, allowing you to search and comment on errors and bug fixes and correlate Sentry errors with metrics and data from your other systems.
Setting up Sentry integration:
By default, Sentry pings the Webhook with event data every time there is a new exception (as opposed to a new instance of an already-logged exception). If you want different (or additional) triggers, you can configure them in the Alerts section of your project settings.
Occasionally, the server name which Sentry reports may not match the host name recognized by Datadog. To overcome this, set a custom value for the server_name
tag, which is attached to each event.
To use a different host name while preserving Sentry’s default server_name
value, set a hostname
tag on your events. See Sentry’s documentation on Customizing Tags for your specific language.
If Sentry errors are missing from Datadog, your Sentry Webhook probably isn’t triggering. This could be due to the following scenarios:
Alerts are only sent when a rule is triggered:
For example, if the rule condition is when “an event is first seen”, an alert is not dispatched until a new issue is created. Depending on how many unique issues your project is receiving, this can take some time.
The notification integration is disabled:
Ensure that the notification integration is enabled under the rule actions, either as the specific service, or covered under “all enabled services”.