Skip to main content

INTEGRATIONS

Plugs into what you already run

Data sources, collectors, notification channels and templates — Nightingale connects to what exists rather than replacing it. The full list is below, and every entry links to how to wire it up.

83Built-in templates
13Data source types
20Notification channels

DATA SOURCES

Data sources

Nightingale ships no storage of its own; it queries what you already run. Metrics stores speak PromQL, log stores use their own query syntax, and SQL stores take plain SQL — alert rules and dashboards work on all three.

NOTIFICATIONS

Notification channels

DingTalk, WeCom, Feishu, email and phone/SMS work out of the box. Slack, Telegram, Discord, PagerDuty and Jira come with built-in message templates — create the media type and send. Anything else goes through a webhook with a custom body.

  • Slack
  • PagerDuty
  • Email
  • Telegram
  • Discord
  • Jira
  • Mattermost
  • Phone / SMS
  • FlashDuty
  • DingTalk
  • Feishu
  • WeCom

COLLECTORS

How data gets in

Nightingale does not collect data itself. The templates above are written for Categraf, but any collector that speaks Prometheus Remote Write can feed it.

CategrafRecommended

One agent for operating systems, middleware, databases and cloud providers. Every built-in template ships its collector config for Categraf.

Categraf docs →

Telegraf / Datadog Agent

Keep what is already running; point its output at the Nightingale Remote Write endpoint.

Collector setup →

Exporters

node_exporter, mysqld_exporter and the rest of the Prometheus ecosystem, scraped by Categraf or Prometheus and written in.

Collector config →

Remote Write directly

Your own programs or the OpenTelemetry Collector push straight to /prometheus/v1/write.

Verify data arrives →

Not seeing what you need?

The template list comes straight from the open-source repo, where a template is one directory: icon, collector config, dashboards, alert rules. Ask for what is missing in an issue, or write one to the spec and send a PR.