Kener Docs
llms.txt
Search Documentation
Search through all documentation pages
Core Concepts

RSS Feed

Public RSS 2.0 feed of recent incidents and scheduled maintenance

Kener exposes a public RSS 2.0 feed of incidents and scheduled maintenance so feed readers, bots, and dashboards can pick up status changes without polling the API.

Feed URLs

URL Scope
/rss.xml Default page (root). Honors forceExclusivity when enabled.
/{page_path}/rss.xml A named status page — only items for that page's monitors.

URLs respect KENER_BASE_PATH, so a deployment at https://status.example.com/status exposes the feed at https://status.example.com/status/rss.xml.

Both routes return:

  • Content-Type: application/rss+xml; charset=utf-8
  • Cache-Control: public, max-age=300

What's in the feed

The feed includes incidents and maintenance events from the last 90 days, capped at 50 most-recent items, sorted by date descending.

Hidden monitors never appear in an item's list of affected monitors. Which items appear depends on the feed:

  • /{page_path}/rss.xml, and /rss.xml when forceExclusivity is on, include an item only when it is global (is_global = YES) or affects a monitor that is on the page, ACTIVE, and not hidden. See Monitor Visibility.
  • /rss.xml when forceExclusivity is off includes every incident and every maintenance event. An item tied only to hidden monitors stays listed and shows no affected monitors.
  • Unknown page_path returns 404.
  • If siteURL is not configured, the feed returns 404.

Item shape

Field Notes
title [Incident] ... or [Maintenance] ...
link Absolute URL to /incidents/{id} or /maintenances/{id}
guid incident-{id} or maintenance-{event_id} — stable, not a permalink
pubDate RFC-822. Incidents use latest comment time (fallback start time); maintenances use scheduled start.
description CDATA-wrapped text: status, affected monitors, latest update or maintenance description

For maintenances, {event_id} is the maintenance event id (one item per recurrence), matching the URLs used elsewhere in the app.

Verify your feed

curl -i https://status.example.com/rss.xml

You should see 200 OK, application/rss+xml, and a <channel> block with one <item> per recent event.