v0.7 Self-host

Every log you have,
one stream.

Nightjar tails every service you run into a single window and keeps the line that matters where you can see it. Rules promote a line; nothing else moves.

nightjar tail --all
Start tailing Read the config

Free for three services. No card, no sales call.

tail --all

Live
  • 08:14:02 info api-gateway accepted 1,204 req in 60s, p99 84ms
  • 08:14:07 ok billing-sync reconciled 318 invoices, 0 drift
  • 08:14:11 fail image-worker upload aborted after 3 retries: connection reset by peer
  • 08:14:11 warn image-worker queue depth 812, above the 500 mark for 4m
  • 08:14:19 info api-gateway cache warm, 41,900 keys resident
  • 08:14:23 ok image-worker retry succeeded, queue draining

A rule promotes a line. Nothing else does.

Every team already ships logs somewhere. What they usually do not have is agreement about which line was worth waking up for, and a place that agreement is written down.

In the repo

nightjar.toml

Rules live in the service they watch and get reviewed like anything else in it. The rule that paged you at 3am is in the diff, with a name on it and a reason underneath.

One window

tail --all

Forty services in one stream, ordered by when the line was written rather than by when it arrived. Clock skew is corrected at ingest, so the order you read is the order things happened.

Nothing is dropped

retained

A promoted line is a view, not a filter. The rest of the stream is still there and still queryable, which is what makes it safe to write an aggressive rule.

Twelve lines, checked in.

One file at the root of the service. Nightjar reads it on every deploy and applies the rules to the stream as it arrives.

  • No agent. It reads the stdout you already write.
  • No new query language. Rules are patterns and thresholds.
  • No silent drop. A rule promotes a line, it never removes one. 
service = "image-worker"

[[rule]]
name    = "upload gave up"
match   = "aborted after * retries"
level   = "fail"
promote = true

[[rule]]
name      = "queue backing up"
metric    = "queue.depth"
above     = 500
sustained = "3m"
level     = "warn"

Point it at one noisy service.

Pick the service you most dread opening. If Nightjar has not found you something you would rather have known within two weeks, delete the file and nothing about your logging changed.

Nightjar is a fictional product. This page exists to show a theme.