How Shankh works
Shankh is used from the web application. After signing in, the available workspace and product access are loaded for your account. Some configuration pages are available only to Admin users.
Sign in
- Open the Shankh web application.
- Sign in with your account.
- Confirm the workspace shown in the navigation is the one you expect.
- Open Dashboard to see active incidents, on-call status and response metrics.
If a configuration page is missing from your navigation, you are signed in as a Member rather than an Admin.
Set up in order
Each step depends on the one before it. Working out of sequence means coming back to finish it.
- Create the workspaces that own your services, add responders, and group them into teams.
- Connect Slack and Telegram, and send a test through each.
- Configure escalation levels, and assign the users and teams that answer each one.
- Schedule on-call per workspace.
- Set up alerting last: connect AWS or another source and put alarms on it.
- Run an end-to-end test before pointing production alerts at Shankh.
Channels come before escalation because a level pointing at a channel that has never delivered is the most common reason a real incident reaches nobody.
Find the area you need
| Area | Use it for |
|---|---|
| Dashboard | Active incidents, on-call status, escalation timers, response metrics |
| Incidents | Active and historical incidents, and full incident detail |
| Escalation | On-call calendar, escalation levels, steps and timings |
| Workspaces | Workspaces, teams, membership and access |
| Channels | Slack, Telegram and user notification setup |
| Cloud Integration | AWS alert setup and alert-management credentials |
| Webhook generator | Ingest URL and API key for direct alert senders |
| Noise dashboard | Alert volume, noisy alerts, flapping, signal-to-noise |
| Reports | Incident timelines, MTTA, MTTR, SLA data, postmortem output |
| Stakeholder view | Live links for non-technical incident updates |
| Mobile setup | Connect the Shankh mobile app |
