Statusly Integrations
Telegram Integration
Availability monitoring for CIS startups. Configure instant downtime alerts and manual health checks directly in your Telegram group or channel.
Bot Setup & Configuration
Deploy the Statusly monitoring bot in under 60 seconds. The bot requires admin privileges to post incident reports, but remains silent during normal operations to keep your workspace clean.
After initiating the handshake with @StatuslyBot, you will receive a unique webhook token. Paste this token into your Statusly dashboard under Project Settings > Notifications. The bot automatically syncs with your existing check configurations, including DNS resolution tests for api.yourproject.ru and SSL certificate expiry tracking for payments.vendor.example.com.
1. Initiate Connection
Open Telegram and search for @StatuslyBot. Tap Start and grant the requested read-only permissions for user identification and chat routing.
2. Select Target Environment
Choose between a private group for dev teams or a public broadcast channel for customer status updates. Cross-posting is supported via Telegram's native forwarding API.
3. Verify Webhook Endpoint
The bot will send a test payload to your configured endpoint. Confirm receipt to activate real-time routing for HTTP 5xx errors and latency spikes above 400ms.
Channel Alert Routing
Granular control over what reaches your main operations channel. Statusly filters noise by default, only pushing verified incidents after a 3-check confirmation cycle to prevent false positives.
Alert templates are fully customizable using Handlebars syntax. Each incident push includes the affected endpoint, current HTTP status code, response time delta, and a direct deep link to the incident timeline. You can configure quiet hours between 02:00 and 06:00 MSK, during which only P1 critical failures bypass the suppression filter.
Incident Payload Structure
Messages include structured fields: service name, region (e.g., Moscow-2), uptime percentage over the last 7 days, and automated rollback suggestions for Nginx configuration errors.
Escalation Matrices
Define tiered notification paths. If the primary channel shows no read receipts within 15 minutes, Statusly automatically forwards the alert to your secondary #ops-escalation group with a high-priority tag.
Recovery Confirmations
Automatic All Systems Operational broadcasts are sent only after 10 consecutive successful checks. Historical MTTR metrics are appended to each recovery message for audit trails.
Interactive Bot Commands
Run on-demand diagnostics without leaving your messaging app. The integrated CLI supports real-time probing of your infrastructure directly from the chat interface.
Type /status to retrieve an aggregated health report across all configured monitors. The output displays current latency percentiles, TLS handshake duration, and certificate validity windows. Use /ping [domain] to execute an instant ICMP and HTTP/2 probe against a specific target. Results are formatted as inline code blocks for easy parsing by DevOps teams.
/status
Generates a comprehensive snapshot of all active monitors. Returns a markdown table with endpoint URLs, current state (operational/degraded/down), and last successful check timestamp. Supports filtering by environment tags like /status --env production.
/ping
Triggers an immediate synthetic transaction against a specified host. Measures TCP connection time, TLS negotiation overhead, and first byte delivery. Example: /ping checkout.stripe-integration.example.com returns detailed waterfall metrics.
/mute & /unmute
Temporarily suppress notifications for maintenance windows. Accepts duration parameters in minutes (e.g., /mute 45) and automatically re-enables routing once the timer expires or manual override is issued.