Skip to Content

Tier 1 Datadog monitors, and log levels Datadog can trust

Shipped 2026-10-26

Monitors

Fourteen monitors live in infra/datadog/monitors/, one JSON file each, to be imported in Datadog. They cover API errors, 5xx responses and silence, the health job and its checks, cron failures, the Stripe webhook, currency send failures and connectors sending invalid JSON. Every one posts to #iba-alerts. infra/datadog/README.md lists them and the import steps.

A field named status overrode the log level

Datadog treats a top-level status attribute as the log level. Four log lines had one:

  • cron_finished (success / failure): a failed run would have been recorded at emergency; a successful one showed as ok.
  • stripe_webhook.unknown_payment (the payment’s succeeded): the “paid but nothing activated” error arrived as OK.
  • mandrill_webhook.event_failed and passcode.sent.

They are now outcome, payment_status, mandrill_status and sent. cron_finished logs at error when a job fails. The logger also renames any remaining status field to status_value, so a new one cannot override the level again.

Stripe heartbeat

Every signed Stripe event answered 200 now logs stripe_webhook.processed with its type, so a day with no Stripe events at all can alert.

Last updated on