-
-
Notifications
You must be signed in to change notification settings - Fork 244
Badges
In v4.1, a cState badge for the general status is available at baseURL.example.com/index.svg
.
In v5.1, you can access badges for individual components. Please make sure you have the correct setup as per the code snippet below. Then go to baseURL.example.com/affected/api/index.svg
(or basically just click open your status page, click on one component (in this case it's API) and then add /index.svg
to the end of the link.
Inspired by shields.io, suggested by cbergmann.
Add the following to your config.yml
:
outputFormats:
svg:
isPlainText: true
mediaType: image/svg+xml
Change your API code to this:
outputs:
page:
- html
- json
section:
- html
- json
- rss
- svg
home:
- html
- json
- rss
- svg
Notice that svg
is now added to the bottom under term
as well as home
.
Still can’t find help? Open issue →
Like cState? Please star it and share it with people who might find it useful!
Use the README to get some basic information about cState.
- cState Core (you are here)
- cState HTML Embed
- cState CLI
- cState Monitor Bot
Please note the Monitor Bot and CLI tools work best with cState version 6 and up.
- Method 1 - Create a new file manually
- Method 2 - Create incident with CLI / SSH
- Method 3 – Create incident from Web UI
Create incidents automatically – Setting up monitoring
Announcing maintenance. Informational posts (pinned or not) [v5.2+]
- Changing site name
- Changing site URL
- Changing site language
- Changing site description
- Changing date formats (v3.0)
- Tabs
- Google Analytics
- Disable complex calculations (v4.1)
- Hiding incident history (v4.2)
- Customize incident history display (v6)
- Uptime histogram (v6)