Operations | Monitoring | ITSM | DevOps | Cloud

Talks about being on call are usually met with complaints. Here's how to alter the narrative and develop a stronger, more compassionate process. A few years ago, I took oversight of a significant portion of our infrastructure. It was a complex undertaking that, if not managed and regulated properly, could have resulted in major disruptions and economic consequences over a large area.

Lack of communication between IT operations and ITSM teams results in data silos. And data silos make it challenging, if not impossible, to solve problems efficiently. One-third of ITOps professionals say that gathering business context is the biggest challenge to effective incident response and management, according to EMA Research.

In today’s digital age, customer expectations are at an all-time high, with demands for instant support, flawless user experiences, and constant service availability. This environment of heightened expectations pushes organizations to innovate and streamline their operations continuously. Ensuring seamless service delivery hinges on the ability to detect and resolve issues swiftly, whether they are server crashes, software bugs, or unexpected outages.

Pets.com was an online pet supply retailer founded in 1998, during the dot-com craze. In February 2000, it raised $83 million to go public based mainly on metrics like user acquisition, website traffic, and brand recognition. However, the profit margins were minimal and the marketing costs exorbitant, which led Pets.com to file for bankruptcy nine months after its IPO. The industry now recognizes these metrics as vanity metrics.

‍ ‍The article discusses streamlining on-call and incident management, focusing on the implementation of a new workflow. One key issue highlighted is the complexity of integrating various tools and platforms used for incident response, which can lead to fragmented communication and delayed resolutions. Another challenge is ensuring the efficiency of escalation protocols, where delays or missteps can impact response times.

‍Handover for on-call schedules in this workflow can be problematic due to inconsistent communication and lack of clear documentation. Misunderstandings can occur when shifts change, leading to missed alerts or incomplete information being passed along. Relying solely on Slack can result in important details being buried in message threads, making it hard to track ongoing issues.

‍Managing PTO and vacation time in on-call workflows can lead to coverage issues, particularly when team sizes are small. Ensuring adequate coverage during local and global holidays can be complex, often requiring shifts to be swapped, which can disrupt team balance. Handling on-call duties during these periods may strain the available staff, potentially leading to fatigue and decreased effectiveness. Coordination and planning become crucial to maintain service reliability and avoid burnout.

Managing PTO and vacation time in on-call workflows faces several issues. Scheduling conflicts can arise when PTO requests overlap with critical on-call periods, leading to inadequate coverage. Automated systems may not always account for last-minute changes, causing potential gaps in availability. Coordination between HR, calendar systems, and on-call schedules can be complex, often resulting in miscommunication.

The article addresses the integration of ticket administration across platforms like Jira, Slack, JSM (Jira Service Management), and PagerDuty to streamline on-call and incident management. However, a potential challenge with such integrations lies in maintaining consistency and synchronization across these disparate systems. Issues may arise from delays or discrepancies in updating ticket statuses between platforms, leading to confusion or duplication of efforts among teams.