In universities around the world, the teachers spend most of their time in the classrom doing what amounts to a monologue. Sure, the students may ask questions, and there may be some interaction but most students don’t. And even when they do, time available for questions and discussion is often very limited.
Yesterday, we’ve announched the Campfire integration via callbacks. Campfire callbacks allow OpsGenie users to push alert activity to Campfire chatrooms as messages.
Couple of weeks ago, we have announced direct integration with HipChat. We’ve been continuing to work on extending OpsGenie callback capabilities.
In operations, most of the time no news is good news. If we’re not receiving alerts from monitoring systems about problems, we tend to assume that all is well with the world. But what if we’re not receiving alerts because some part of our monitoring solution has not been working for days or even weeks? If you’ve ever found out about a problem with the monitoring systems after being asked why there was no alert for a particular problem, you know what I’m talking about. If you’re supporting a web based application or service, chances are you’re employing a monitoring service to monitor the availability of your application from the outside, preferably from multiple locations. At OpsGenie we do take advantage of external services to monitor availability of OpsGenie web UI, as well as the API end points. External web monitoring enables us to find out quickly when there is a problem with OpsGenie. In addition, OpsGenie has supported what we can “heartbeat monitoring" since the beginning. Heartbeat monitoring enables OpsGenie users to send OpsGenie periodic heartbeat messages. Heartbeat monitoring serves multiple purposes: