PagerDuty and Opsgenie bridge for StillOnline
At some point, “send me a Telegram alert” becomes too small for the team. You may need escalation, schedules, acknowledgements, or a shared on-call history.
StillOnline can remain the lightweight monitor and public status page. PagerDuty or Opsgenie can handle the escalation layer through email or Slack routing.
Quick answer
StillOnline owner alerts support email, Telegram, and Slack; Free includes one channel and Pro/Ultimate include all three on pricing. PagerDuty documents email integrations in PagerDuty email integration, and Atlassian documents Opsgenie email integrations in Opsgenie email integration. Use StillOnline for the HTTP check and status page, then route a copy into your on-call tool when escalation matters.
When a bridge makes sense
Do not add an on-call platform just because it sounds mature. Add it when a real process needs it.
| Signal | Stay with StillOnline channels | Bridge to on-call tool |
|---|---|---|
| One founder | Telegram or email | Usually no |
| Two operators | Telegram + Slack | Maybe |
| Rotation exists | Slack/email copy | Yes |
| Compliance asks for history | Status page + logs | Yes |
Email bridge
Both PagerDuty and Opsgenie can create incidents from email. Point a StillOnline owner alert email to the integration address, then tune rules so only production monitors create on-call incidents.
Keep staging, demo, and low-priority monitors out of the escalation path. They can still alert you in Slack or Telegram.
Slack bridge
If your on-call tool listens to Slack commands or workflows, route the StillOnline Slack alert into a dedicated channel. The channel should be quiet enough that every message is actionable.
For customer communication, publish updates on the StillOnline status page instead of treating PagerDuty notes as customer-facing text.
Related guides
- Solo founder on-call without PagerDuty
- Slack uptime alerts webhook
- Status page security questionnaire
- Side project production monitoring checklist
FAQ
Does StillOnline replace PagerDuty or Opsgenie?
No. StillOnline is a lightweight uptime monitor and status page for small SaaS teams. PagerDuty and Opsgenie are escalation systems when you need rotations, acknowledgements, and audit history.
Can StillOnline create PagerDuty incidents?
Use an email integration or a Slack bridge. Treat it as routing from StillOnline alerts, not as a native PagerDuty connector.
Which StillOnline alerts should page the on-call tool?
Only production checks with customer impact. Staging and internal tools should use lower-noise channels, or you will train the team to ignore pages.
Do customers see PagerDuty or Opsgenie updates from StillOnline?
No. Customers should see the public status page and incident posts. Keep escalation notes internal and write customer updates separately.