Status Badges
Status badges provide a visual way to display the real-time status of your monitors and heartbeats. These badges are perfect for embedding in README files, documentation, status pages, or any website where you want to show the current health of your services.What are Status Badges?
Status badges are small SVG images that dynamically show the current status of your monitors or heartbeats. They update in real-time and can be embedded anywhere that supports images, making it easy to communicate service health at a glance.Badges are publicly accessible and don’t require authentication, making them perfect for public repositories and status pages.
Badge Types
Upcron.io provides badges for both monitors and heartbeats:Monitor Badges
Display uptime status for your websites and APIs
- Up: Green badge showing service is operational
- Down: Red badge indicating service is unavailable
- Unknown: Gray badge for undetermined status
Heartbeat Badges
Show status for your cron jobs and scheduled tasks
- OK: Green badge showing job is running on schedule
- Late/Failed: Red badge indicating missed or failed job
- Pending: Yellow badge for jobs in progress
Getting Badge URLs
For Monitors
1
Navigate to Monitor
Go to your monitor’s detail page in the Upcron.io dashboard.
2
Find Badge Section
Look for the “Badge” or “Status Badge” section on the monitor details page.
3
Copy Badge URL
Copy the provided SVG badge URL. It will look like:
For Heartbeats
1
Navigate to Heartbeat
Go to your heartbeat’s detail page in the Upcron.io dashboard.
2
Find Badge Section
Look for the “Badge” or “Status Badge” section on the heartbeat details page.
3
Copy Badge URL
Copy the provided SVG badge URL. It will look like:
Using Badges
In README Files
Add badges to your repository’s README file using Markdown:In HTML
Embed badges in HTML pages, documentation, or status pages:In Documentation Sites
For documentation platforms like GitBook, Notion, or Confluence:- GitBook
- Confluence
- Notion
Badge Customization
URL Parameters
Customize badge appearance using URL parameters:Available Parameters
| Parameter | Description | Example Values |
|---|---|---|
style | Badge style | flat, flat-square, plastic |
label | Custom label text | API, Website, Service |
up_color | Color when service is up | green, brightgreen, success |
down_color | Color when service is down | red, critical, important |
unknown_color | Color for unknown status | lightgrey, inactive |
Style Examples
- Default
- Flat Square
- Custom Colors
- Custom Label
Badge Status Meanings
Monitor Badges
🟢 UP
Service is operational and responding correctly
🔴 DOWN
Service is not responding or returning errors
⚪ UNKNOWN
Status cannot be determined or monitor not yet checked
Heartbeat Badges
🟢 OK
Job is running on schedule
🟡 PENDING
Job is currently running
🔴 LATE
Job missed its scheduled time
⚪ NEW
Newly created heartbeat, not yet checked
Best Practices
1. Choose Meaningful Labels
Use descriptive labels that clearly indicate what’s being monitored:2. Group Related Badges
Organize badges logically in your documentation:3. Link to Detailed Status
Make badges clickable to link to detailed status information:4. Keep Alt Text Descriptive
Use meaningful alt text for accessibility:Common Use Cases
GitHub Repository
Show the health of your deployed application:Company Status Page
Create a simple status page with just badges:Documentation Integration
Add service status to your API documentation:Internal Dashboard
Embed badges in internal tools or dashboards:Caching and Performance
Badge Caching
Badges are cached for optimal performance:- Cache duration: 60 seconds
- CDN delivery: Global content delivery network
- Automatic updates: Status changes reflect within 1-2 minutes
Browser Considerations
Some browsers may cache images aggressively. To ensure fresh data:Troubleshooting
Badge not updating
Badge not updating
Possible solutions:
- Check if the monitor/heartbeat ID is correct
- Verify the badge URL is accessible
- Clear browser cache or add cache-busting parameter
- Wait up to 2 minutes for status changes to propagate
Badge showing as unknown
Badge showing as unknown
Common causes:
- Monitor or heartbeat hasn’t been checked yet
- Invalid monitor/heartbeat ID in the URL
- Monitor is inactive or disabled
- Recent configuration changes still propagating
Custom styling not working
Custom styling not working
Check these items:
- URL parameters are properly encoded (spaces as %20)
- Parameter names are spelled correctly
- Color values are valid (use standard color names or hex)
- Style parameter matches available options
Badge not displaying in README
Badge not displaying in README
GitHub/GitLab specific:
- Ensure the URL is publicly accessible
- Check if the image URL is properly formatted in Markdown
- Try accessing the badge URL directly in your browser
- Some platforms may cache README content