From 79ddc0f8cdc3980071560b7c9b30dad9f48235f1 Mon Sep 17 00:00:00 2001 From: James Brooks Date: Wed, 12 Aug 2026 13:30:25 +0100 Subject: [PATCH 1/2] Document status page badges --- docs.json | 1 + v3.x/guide/status-badges.mdx | 42 ++++++++++++++++++++++++++++++++++++ 2 files changed, 43 insertions(+) create mode 100644 v3.x/guide/status-badges.mdx diff --git a/docs.json b/docs.json index c27b313..e0ba5a1 100644 --- a/docs.json +++ b/docs.json @@ -33,6 +33,7 @@ "pages": [ "v3.x/guide/incidents", "v3.x/guide/components", + "v3.x/guide/status-badges", "v3.x/guide/schedules", "v3.x/guide/metrics", "v3.x/guide/subscribers", diff --git a/v3.x/guide/status-badges.mdx b/v3.x/guide/status-badges.mdx new file mode 100644 index 0000000..b286277 --- /dev/null +++ b/v3.x/guide/status-badges.mdx @@ -0,0 +1,42 @@ +--- +title: 'Status badges' +description: 'Embed the current Cachet system or component status in an SVG badge.' +icon: 'badge-check' +--- + +Cachet can generate cacheable SVG badges that show the current overall status or the status of an individual component. +Use these badges in a README, project page, or any other place that supports an image URL. + +## Overall status badge + +Append `/badge.svg` to your status page URL: + +```html +Current system status +``` + +If Cachet is installed below a path, include that path in the URL. For example, an installation served at +`https://example.com/status` has its badge at `https://example.com/status/badge.svg`. + +## Component status badge + +Append `/components/{component}/badge.svg`, replacing `{component}` with the component ID: + +```html +API status +``` + +Only enabled components that are publicly visible have badges. A badge request for a disabled component or a component +in a non-public group returns `404 Not Found`. + +## Badge styles + +Choose a style by passing the `style` query parameter. Cachet supports `flat-square` (the default), `plastic-flat`, +`flat`, `plastic`, `social`, and `svg`. + +```html +API status +``` + +Badge responses are cached for 60 seconds, so they remain current without requiring every visitor to trigger a new +render. From 8c634360353e41629c63cd3d21c420acf6031bab Mon Sep 17 00:00:00 2001 From: James Brooks Date: Thu, 13 Aug 2026 09:23:33 +0100 Subject: [PATCH 2/2] Update docs.json --- docs.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs.json b/docs.json index e0ba5a1..e1c9af6 100644 --- a/docs.json +++ b/docs.json @@ -33,14 +33,14 @@ "pages": [ "v3.x/guide/incidents", "v3.x/guide/components", - "v3.x/guide/status-badges", "v3.x/guide/schedules", "v3.x/guide/metrics", "v3.x/guide/subscribers", "v3.x/guide/webhooks", "v3.x/guide/mcp", "v3.x/guide/users", - "v3.x/guide/dashboard" + "v3.x/guide/dashboard", + "v3.x/guide/status-badges" ] }, {