PagerDuty Automation

Incident Manager. We are monitoring our Edge connector node logs that are sent to Elastic. If there are any alerts based on our rules that triggers the PagerDuty incident. Then PagerDuty will create the Jira Ticket and send an alert in Slack with detailed instructions and the Jira ticket link with Elastic Cloud log with filters.

Yes. All our edge connector alerts are organised in PagerDuty, we are getting alerts on time in our Slack channels to investigate the issues, which makes our environment more stable, so we are able to provide good values for our customers. Maintain a healthy infrastructure to ensure end-to-end connectivity with minimal interruption.

We are using multiple integrations like Jira, Elastic, Slack, and AWS. Based on an alert from Elastic, creates an incident that makes the Jira ticket execute the runbook if required. Notify the Slack channel with the ticket and Elastic log filter links. With the Slack bot integration, our developer can collaborate in a Slack channel to resolve the incident.

We are not using mobile application for now. We are using rundeck for runbook automation, also we are using rundeck as job scheduler for various sync process runs in background for Database synchronzation and reporting. Major incidents flow via jira, slack then it triggers the aws Lambdas. In some case it triggers the rundeck job.

In our org we use event analytics dashboard to track the daily events and its breakdown based on Type and Integrations. In Dashboard we mainly focus on Service uptime, MTTR and Incidents by services