Oncall can become a high stress environment. In such a scenario, going through tons of several documentations in order to resolve a highly critical issue can be time consuming and challenging. The oncall automation bot to an extend tries to resolve this issue
What it does
- PD auto response The bot mointers the internal documentations by periodically checking the SHA hash value of the documentation website. If the current SHA hash of the site doesn't match with the previous value, it indicates that the website has been modified Whenever there is an update in the content, a web scrapping module is invoked. It scrapes the data and updates the PostgreSQL database
https://test-documentation101.netlify.app/ ↓↓↓ (scrapes content from documentation and saves it to db) ↓↓↓
Slack’s Real-Time Messaging API (RTM API) allows us to receive events from Slack in real-time. The slack bot constantly checks for pagerduty alerts. When a PD alert is triggered, the bot checks in the database to see if there is a match for the triggered incident in the documentation. If yes, it directly sends the alert resolution steps as a thread This would save the oncall engineer from the hustle of going through multiple documentations to resolve a particular issue

Log in or sign up for Devpost to join the conversation.