| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
- Add /api/reload endpoint that triggers configuration reload
- Always requires API key authentication (even if api.access is public)
- Returns error if no API keys are configured
- Update config.example.yaml with new endpoint and {group}/{name} format docs
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GET /api/badge/{name}.svg - Shields.io style status badges (always public)
Options:
- ?label=Custom - Override the label text (default: monitor name)
- ?style=flat|plastic - Badge style (default: flat)
- ?type=status|uptime - Show status or uptime percentage (default: status)
Colors:
- Green (#22c55e) for up / >=99% uptime
- Yellow (#eab308) for degraded / >=95% uptime
- Red (#ef4444) for down / <95% uptime
- Gray (#9ca3af) for unknown
Example: 
|
| |
|
|
|
|
|
|
|
|
| |
New endpoints:
- GET /api/health - Simple health check, always public (for load balancers)
- GET /api/summary - Lightweight status overview (counts + overall status)
- GET /api/uptime/{name}?period=1h|24h|7d|30d|90d - Historical uptime stats
- GET /api/incidents?filter=all|active|resolved|scheduled - List incidents
All new endpoints (except /api/health) follow api.access rules.
|
| |
|
|
|
|
|
|
|
|
| |
Replace N+1 API calls (1 status + N history) with a single /api/page
endpoint that returns all monitor data including history ticks.
For 20 monitors: 21 requests -> 1 request per refresh interval.
The /api/page endpoint is automatically public when refresh_mode=api,
regardless of api.access setting, to ensure the page can always refresh.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Add display.refresh_mode option:
- 'page' (default): Full page refresh via meta refresh
- 'api': Fetch /api/status and update DOM without reload
Also add display.refresh_interval (default: 30s, min: 5s)
API mode updates: status indicators, response times, uptimes,
errors, overall status banner, and page title counts.
History bars remain static until full page refresh.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add configurable access control for /api/* endpoints:
- public: Anyone can access (default, backwards compatible)
- private: API endpoints return 403 Forbidden
- authenticated: Requires API key via X-API-Key header or ?api_key= param
Config example:
api:
access: authenticated
keys:
- "secret-key-1"
- "secret-key-2"
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Support defaulting any monitor option at group level:
- expected_content, body (HTTP/HTTPS)
- ping_count (ICMP)
- dns_server, record_type (DNS)
- graphql_query, graphql_variables (GraphQL)
- db_type (Database)
Only name, type, target, link, reset_on_next_check, expected_ips,
and expected_cname remain monitor-specific (not defaultable).
|
| |
|
|
|
|
|
|
|
| |
Add support for setting these options at group level:
- hide_ssl_days, hide_ping, round_response_time, round_uptime
- method, user_agent, headers, expected_status
This allows configuring common settings once per group instead of
repeating them on every monitor.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add support for loading and applying OpenCode-compatible themes via URL.
Fetches theme JSON, resolves color references, generates CSS variables
and Tailwind class overrides to apply the theme seamlessly.
Features:
- Add theme_url config field under site section
- Fetch and parse OpenCode theme.json format
- Generate CSS custom properties (--theme-*) for all theme colors
- Generate Tailwind class overrides to apply theme colors
- Support both light and dark modes
- Template.CSS type for safe CSS injection
Example usage:
site:
theme_url: "https://raw.githubusercontent.com/anomalyco/opencode/.../opencode.json"
Theme schema: https://opencode.ai/theme.json
|
| |
|
|
|
|
|
|
|
|
| |
Previously, monitors with the same name in different groups would fail
validation. This restriction has been removed to allow duplicate names
across groups, restoring the original behavior.
Note: Monitors with duplicate names will share the same data in the
database since MonitorName is used as the identifier. A future
enhancement could use group+name as a composite key.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add three new monitor types with full support:
- ICMP: Ping monitoring with configurable packet count, tracks packet
loss and average RTT. Marks degraded on partial packet loss.
- DNS: DNS resolution monitoring supporting A, AAAA, CNAME, MX, and TXT
records. Optional custom DNS server and validation of expected IPs/CNAME.
- GraphQL: GraphQL endpoint monitoring with query execution, variable
support, error detection, and content validation.
All new monitors include retry support, response time tracking, and
integrate with existing display options (round_response_time, etc).
GraphQL monitors also support SSL certificate tracking.
|
| |
|
|
|
|
| |
Add monitor-level option to disable hover tooltips on individual ping bars.
Can be set at group defaults or per-monitor. When enabled, visual appearance
remains unchanged but tooltips no longer appear on hover.
|
| | |
|
| | |
|
| |
|
|
| |
hide/round options
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|