Believe it or not, there is a difference between incident closure and incident resolution. Incident closure ensures a problem has been addressed. Comparatively, incident resolution goes a step further by ensuring an incident is closed and all stakeholders are satisfied with the end results and agree with the incident closure.
Over the years here at Statuspage we’ve probably heard every version of the open source vs. paid status page argument. While we’re obviously fans of the SaaS model, we also know there are a lot of advantages to an open source status page for a lot of teams. We’ve even recommended that route to some potential customers we thought would have a better experience hosting their own open source page.
The other day, a newer Engineering Manager here at PagerDuty, Dileshni Jayasinghe, started a Slack thread expressing joy at how fantastic our engineering team is after attending a conference with engineering folk from other organizations. She explained that she’d shared our practice of owning what we build with someone—who then responded by gazing off into the distance and saying, “That’s my dream.”
With businesses collecting millions of metrics, let’s look at how they can efficiently scale and deal with these amounts. As covered in the previous article (A Spike in Sales Is Not Always Good News), analyzing millions of metrics for changes may result in alert storms, notifying users about EVERY change, not just the most significant ones. To bring order to this situation, Anodot groups correlated anomalies together, in a unified alert.
Your incident management process is greatly impacted by the tools you have available. And technology is key when it comes to gaining visibility and obtaining contextual data. You need tools to send alerts when incidents arise, as well as track activity for compliance reporting purposes. Whether you’re in healthcare, information technology or work at a small MSP – you need a robust incident management platform that gives you results and helps mitigate MTTR.
Antiquated pieces of technology create setbacks in every industry, and in healthcare – it’s the pager! Pagers are still being used even though they’re not HIPAA compliant and the infrastructure supporting them is dying out. That’s why doctors and healthcare personnel alike need an advanced way to communicate and protect patient information. Here are six reasons to think of pager replacement options.
An incident postmortem is an excellent framework for learning from incidents and turning problems into progress. It also builds trust with customers, colleagues, and end users (basically the folks affected by the incident) and lets them know your team is working to minimize future incidents and impact.
In the entertainment world, building enterprise apps involves many challenges, such as compatibility with numerous devices and large files like HD videos, along with streaming media to millions of users simultaneously. But today’s entertainment apps are possible only because of a modern approach to software delivery—DevOps brings greater efficiency across the development pipeline.
The healthcare industry is currently laden with pagers. The joke is that not even drug dealers use pagers any more. However, almost 80% of doctors do use pagers. The main problems with pagers is that they impede efficient clinical communications and lack security. Here are 6 ways to improve clinical communications.
