Operations | Monitoring | ITSM | DevOps | Cloud

Alerting

Do More and Work Where You Are With Our New Integration for Jira Server and Data Center

Many of you may be reading this blog from home, a remote office somewhere, a family member’s house, or—if Zoom backgrounds are to be trusted—the cockpit of the Millennium Falcon. We’re all learning how to get better at “working where we are,” and that includes optimizing the tool stack you use each day.

Sticking to Your SLAs with FireHydrant Runbooks

In today’s world, systems are increasingly becoming more and more complex. Due to this complexity, it’s no longer a matter of “if” our systems will fail but “when”. To manage expectations for when our systems do fail, we can look no further than our Service Level Agreement.

Incident Response with Atlassian's Opsgenie

Learn all about Incident Response with @Atlassian 's Opsgenie. Respond to incidents from the Incident Command Center, identify potential root cause from the Incident Investigation view, and keep track of key information within the Incident Timeline. Once resolved, easily fill out the postmortem template and export to Confluence.

Zenduty - Microsoft Dynamics Integration

Microsoft Dynamics is a line of enterprise resource planning and customer relationship management software applications. Microsoft markets Dynamics applications through a network of reselling partners who provide specialized services. Microsoft Dynamics forms part of "Microsoft Business Solutions". The Zenduty-Dynamics integration helps you escalate critical cases/incidents to the right team, proactively alert them about SLA violations and bring in SMEs and stakeholders into high priority cases. To know more about the Integration,

Balancing IT Priorities in Uncertain Times

In recent years, digital transformation projects have dominated the tech priorities of most IT departments – and rightfully so given that they are tasked with ensuring their organizations stay relevant in a fast-changing world where customer expectations are soaring, and agility is everything. However, the COVID-19 pandemic has thrown a curveball to businesses around the globe.

Prometheus for multi-cluster setups

This tip is for those who are using Prometheus federation to monitor multiple clusters. How should alertmanager be configured for multiple clusters? Let us say that if there’s an issue for Cluster A it only needs to send an alert for cluster A? In such cases, every alert should be routed to proper team based on labels (if there is problem with application A on cluster B - team responsible should be notified). In the above case, two alerts are triggered by the same rule.