Operations | Monitoring | ITSM | DevOps | Cloud

%term

Intro

I needed a tool to alert me when my cron jobs silently fail. There is already a number of existing services for this, but it seemed like a fun thing to build myself. So I present to you: healthchecks.io. I am using this myself and it has already been useful for me a couple times. Say, a seemingly benign code change in one service causes my batch job to fail 12 hours later, in the middle of night.

Top 10 Reasons AlertOps is Better Than PagerDuty: #2

A service-level agreement (SLA) defines the level of service expected from a service provider. As such, an SLA plays a key role in an organization’s ability to fulfill customer requests. If an organization breaks an SLA, it risks significant revenue and brand reputation damage. Perhaps worst of all, this organization may lose customers to its rivals if it cannot comply with SLA mandates.

Top 10 Reasons AlertOps is Better Than PagerDuty: #3

AlertOps offers more flexibility than our competitors when it comes to alerting capabilities – and that can mean more power for our users. Does your incident management team have the ability to send the right messages, to the right team members, every time? If not, team members may be forced to deal with alert overload due to the sheer volume of notifications that they receive over time. In many instances, an entire incident management team receives notifications.