connectors

Your stack isn't a compatibility question.

Nightswatch is built around a pluggable connector layer. Telemetry sources and delivery channels are adapters — the investigation engine never changes. Adding a new source or a new channel doesn't touch how alerts are triaged, how hypotheses are tested, or how the report is written. Your stack is a configuration detail.

Telemetry & alerting

Where the alerts come from and where the evidence is queried.

  • Prometheus

    Point your alert routing at a Nightswatch webhook and grant read-only query access.

  • Alertmanager

    Point your alert routing at a Nightswatch webhook and grant read-only query access.

  • New Relic

    Point your alert routing at a Nightswatch webhook and grant read-only query access.

  • Datadog

    Point your alert routing at a Nightswatch webhook and grant read-only query access.

  • Grafana

    Point your alert routing at a Nightswatch webhook and grant read-only query access.

  • CloudWatch

    Point your alert routing at a Nightswatch webhook and grant read-only query access.

  • Loki

    Point your alert routing at a Nightswatch webhook and grant read-only query access.

  • Splunk

    Point your alert routing at a Nightswatch webhook and grant read-only query access.

  • OpenTelemetry

    Point your alert routing at a Nightswatch webhook and grant read-only query access.

Delivery & response

Where the finished RCA shows up and where feedback comes back from.

  • Slack

    Authorize the connector and pick the channel or address the RCA should land in.

  • Microsoft Teams

    Authorize the connector and pick the channel or address the RCA should land in.

  • PagerDuty

    Authorize the connector and pick the channel or address the RCA should land in.

  • Opsgenie

    Authorize the connector and pick the channel or address the RCA should land in.

  • Email

    Authorize the connector and pick the channel or address the RCA should land in.

  • Webhooks

    Authorize the connector and pick the channel or address the RCA should land in.

How connecting works

  1. 1. Connect

    Give the connector credentials. They're encrypted at rest and verified on setup, so a bad key fails at configuration time rather than at 3am.

  2. 2. Point alerts at your tenant webhook

    Your alerting layer already knows how to POST somewhere. Send it here — the payload is verified by signature or token.

  3. 3. RCAs arrive where your team talks

    The report is delivered to the channel you chose, with feedback buttons attached.

Don't see your stack?

It's one connector away — the adapter interface is deliberately small. Tell us what you run and we'll talk about what connecting it looks like.