Overview
How Courier connects to Datadog
Datadog is the observability platform your team already uses to watch application health: metrics, logs, dashboards, and alerts in one place.
Courier forwards your notification metrics and logs to Datadog, so you can build dashboards and alerts on delivery health alongside the rest of your stack.
You need a Courier account and a Datadog account with an API key.
Why monitor in Datadog
What you get with Datadog + Courier
Delivery metrics and events
Courier emits sent, delivered, failed, undeliverable, opened, and clicked events, plus filtering, throttling, and receipt metrics, into Datadog.
Build delivery dashboards
Chart delivery, open, and click rates over time in Datadog, right next to your app and infrastructure dashboards.
Alert on failures and bounces
Use Datadog monitors to page or notify your team when failures or undeliverable rates spike, using the same alerting you already trust.
Watch per-channel health
Email, SMS, push, and direct message each report delivered, sent, error, and undeliverable status, so you can track health channel by channel.
Correlate with app performance
Sit notification delivery next to request latency, error rates, and deploys, so you can see whether a delivery dip lines up with an app issue.
Automation, users, inbox, and lists
Automation invocations and throttling, user and account activity, inbox connections, and list subscriptions all flow through as metrics too.
Use cases
What teams monitor with it
Setup
Connect it in minutes
An admin adds Datadog once in Courier. Metrics start flowing from the moment you connect it, so turn it on before you need the insights.
FAQ
Frequently asked questions
Can I monitor my Courier notifications in Datadog?
Yes. Courier's Datadog integration sends your notification metrics out to Datadog so you can watch delivery health next to your other services. Datadog is a monitoring destination here, not a channel Courier delivers through.
What Courier data shows up in Datadog?
Courier emits metrics under the courier. namespace covering message volume and engagement. Examples include courier.message.sent, courier.message.delivered, courier.message.total.opened, and courier.message.total.clicked, plus automation counters like courier.automation.invoked, and more.
How do I connect Courier to Datadog?
In the Courier integrations catalog, open Datadog and paste a Datadog API key, then set the site parameter to match your Datadog instance URL. Configure it per environment, since test and production forward metrics separately.
Will Datadog show my past Courier notifications?
No. The integration is forward-only: Courier starts emitting metrics the moment you activate it and does not backfill historical data. Anything sent before you connect will not appear, so enable it before you need the history.
Can I see Courier delivery metrics broken out by channel?
Yes. Alongside aggregate message metrics, Courier reports per-channel counters so you can compare delivery across channels. Examples include courier.email.sent, courier.email.delivered, courier.sms.delivered, and courier.push.sent, making a failing channel easy to spot.
What can I build with Courier data in Datadog?
You can build dashboards and monitors on the forwarded metrics and alert when delivery or open rates drop. Courier also provides a downloadable dashboard JSON starter kit to visualize your notification metrics without building every panel yourself.
Does Courier send notifications through Datadog?
No. This is one-way monitoring: metrics flow out of Courier into Datadog for observability only. Courier still delivers your notifications through email, SMS, push, and Courier Inbox; Datadog just tracks how they perform.
More
