- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`
If your application does not have an existing Datadog integration, and you don’t want to create a custom Agent check, you can send events with email. This can also be done with messages published to an Amazon SNS topic; read the Create Datadog Events from Amazon SNS Emails guide for more information.
Before you can send events with email, you need a dedicated email address from Datadog:
Plain text
or JSON
).The Events API emails section displays all the emails available for your applications and who created them.
Name | Description | Example |
---|---|---|
Description | A description of the email’s purpose. | “Used for MyService notifications” |
Tags | List of tags to be appended to each event received through the email. If other tags are present in the JSON message, they are all added. There is a limit of 20 tags per email. | tag1:val1 , tag2:val2 |
Recipients | List of handles to be added to the beginning of the message for all events created through the email, without @ prefix. For more information, see Notification recipients.There is a limit of 10 recipients per email. | my@email.com , slack-acc-ch |
Alert Type | The alert type for events created from the event email. When present, the alertType field in a JSON email takes precedence over any other alertType values. | Info |
There are two different ways to send events with email:
If you have complete control over the email sent by an application, then you can use configure a JSON-formatted message. This format allows you to set everything in the event that appears in Datadog.
With a JSON-formatted email, the following fields are controllable:
Note: If your JSON is not properly formatted, or the email is sent without a subject, the event doesn’t show in your event stream.
In a JSON-formatted email, the subject of the email doesn’t appear in the event. The value of the title attribute is used for the event title. All data that appears in the event should be defined in JSON in the body of the email. Furthermore, the body must be pure, well-formed JSON—if not, the message is ignored. Example event sent with JSON:
Note: If you are testing the email with a standard email client, the body may be converted to HTML. This causes the body to no longer be pure JSON, resulting in an ignored email.
If you have little control over the email sent by an application, use a plain text formatted message.
With a plain text formatted email, the following fields are controllable:
Field | Required | Description |
---|---|---|
Sender email address | Yes | The email address of the sender |
Subject | Yes | The subject of the email |
Body | Yes | The body of the email |
For example, the email below is a valid submission:
Sender's email: matt@datadog.com
Subject: Env:Test - System at 50% CPU - #test
Body: This is a test message showing that env:test is at 50% CPU - #test
The email body goes through several cleanup steps to enhance readability and security. The expected changes include:
a
, br
, code
, div
, em
, h1
, h2
, h3
, h4
, h5
, h6
, hr
, iframe
, img
,
li
, ol
, p
, pre
, span
, strong
, ul
. Any other HTML tag, including strings enclosed in <>
, are removed.The subject of the email becomes the title of the event and the body of the email becomes the event message. The sender of the email appears at the bottom of the event. Tags can be added by using #
in message body. Example event sent with plain text:
Datadog event text supports Markdown but embedding HTML in Markdown is not supported. To use Markdown in the event text, start the text block with %%% \n
and end the text block with \n %%%
:
{
"title": "Did you hear the news today?",
"text": "%%% \n [an example link](http://example.com/session_id \"Title\") \n %%%",
"priority": "normal",
"tags": ["environment:test"],
"alert_type": "info"
}
If you are embedding a link in a Markdown block, make sure the URL is encoded properly:
# Not encoded
http://example.com/session_id:123456
# Encoded
http://example.com/session_id%3A123456
The maximum allowed email size, including content and attachments, is 20MB. Emails exceeding this limit are ignored.
To understand which emails are being used and receiving events, check the Last Used
column in the Events API Emails tab in organization settings. This displays the most recent date that an email was processed for each address, or No data
if there are no records of it being used.