Getting started

What Nightlamp does

Every event your app emits — a Sentry exception, a Promtail log line, a CloudWatch error — gets normalized, fingerprinted, and grouped into an Issue. When ingestion patterns indicate a real outage, Nightlamp opens an Incident: an ops alert plus a customer-facing notification on the same incident timeline.

Native uptime monitoring runs in parallel — every minute, an HTTP probe checks your public URL from us-east-1 and rolls the results into 24h / 7d / 30d / 90d uptime aggregates. No bring-your-own UptimeRobot needed.

For CI, internal tools, or agent-driven setup, every app also exposes a capabilities manifest that lists supported monitors, webhook interfaces, ingestion endpoints, rotation paths, and status readback routes.

The four integration paths

Pick the path that matches your stack — they're additive, not exclusive.

1. Errors via Sentry SDK

   Drop the Sentry SDK into your app, point it at your Nightlamp DSN, and exceptions land in your Issue queue within seconds. Works with every @sentry/* client (JS, Python, Go, Ruby, etc.). SDK integration →

2. Logs via Promtail / Fluent Bit / CloudWatch

   Stream structured logs from k8s, Lambda, or any service that speaks the Loki push API. Each log line gets the same fingerprinting + grouping as SDK events. Log subscriptions →

3. Native uptime + GitHub releases

   Auto-configured the moment you register an app — no setup. Optional: add a GitHub webhook to track deploys, so incident timelines show "started 4 minutes after release v1.42.0".

4. AgentDraft + email-flow monitors

   Connect an AgentDraft mailbox when you need to prove magic-link, OTP, signup confirmation, or email round-trip flows work end to end. Enable the QA mailbox, then create an email_flow monitor. AgentDraft guide →

Where to go next

Sign in to see your apps. The same DSN flow applies whether you're on the baseline tier or white-glove.