Repository navigation
Nightbell 3.18.0
A new monitor kind, Health endpoint, reads a report your service writes about itself. A status code only says the server answered. This says which part is in trouble, the rule that decided it with the value it measured, and what the service saw along the way. The overall verdict pages you; the rest is what you read when it does.
The format is one JSON document, described in docs/health-format.md with a JSON Schema beside it and a drop-in writer for ASP.NET Core. The body decides, not the status code, so a 503 carrying a report is read as that report. An existing ASP.NET health check that answers plain Healthy, Degraded or Unhealthy works before you write any JSON.
Signing in: the endpoint stays behind whatever protects the rest of your API. Nightbell signs in the way your own clients do: a fixed header, basic auth, or single sign-on through your web app, a username and password, a service account or a pasted refresh token. Tokens and secrets are encrypted on the phone and never go into a backup. When you type the address, Nightbell tries it once without signing in, so setup can tell you whether it needs a sign-in at all.
What it claims, and what it does not:
| Situation | Card | Pages |
|---|---|---|
| Nightbell's own sign-in ended, or its password was refused | Not checking · Sign in needed | No, a reminder once a day |
| The sign-in server cannot be reached | Down, "Sign-in server unreachable" | Yes |
| A fresh token and the API still refuses it | Down | Yes |
On the detail screen the Components card is a bar of down, degraded and up parts, then one row per part. Only the worst part opens on its own, with its rules and its log; the rest are one tap away.
Also in this release: a store this version cannot read, such as one written by a newer version, is kept instead of having an empty one written over it, so the monitors in it are still there for a version that can read them. The README now lists every monitor kind, Prometheus included.