This article is part of a series on setting up an end-to-end monitoring and alerting stack using Prometheus. Continuing our series on setting Prometheus in a Docker container, we will add a Grafana instance to our Prometheus setup. Please refer to the previous article where we use docker compose to run Prometheus and Alertmanager together as that forms the basis to run multiple related containers. We will add a container to run Grafana to the same compose file in this article.

This blog post will uncover how ilert status pages work, the challenges we encountered while developing this feature, and the problem-solving approaches we adopted.

In January 2025, The Network & Information Security Directive (NIS2) goes into effect. This Directive requires organizations across the EU and those that serve EU customers to strengthen their cybersecurity posture.

Managing incidents effectively is not just about responding to alerts; it’s about building a resilient system that thrives on continuous improvement. Modern organizations operate in complex environments where even minor disruptions can escalate into major issues. This calls for a proactive approach that leverages data and automation to optimize the entire incident response lifecycle.

Understanding what went wrong, what went right, and how to improve is crucial for IT teams striving for excellence. But as teams evaluate their processes and outcomes, they often encounter two tools for reflection: postmortems and retrospectives. While they may seem similar at first glance, their objectives and applications differ significantly. Let’s dive into the nuances of retrospective vs. post mortem and explore why both hold a pivotal place in team growth and project success.

In today’s digital world, IT is not a ‘nice-to-have’ but the backbone of every company. Streamlined IT operations are therefore essential for success and even survival. However, technical faults and failures are unavoidable. This is where IT alerting comes into play – a crucial component of IT service management that helps to identify and resolve problems quickly.

Today, every enterprise is digital. Regardless of industry, every business must incorporate digital technologies and strategies into its operations to remain competitive. Maintaining reliable IT infrastructures and digital services while minimizing downtime due to unplanned outages is critical to business success.

One of the most frequent questions I receive from customers is, “What are the best practices to represent my services in PagerDuty?” This question is not easy to answer, but there is a general consensus that the representation needs to be both accurate and visually appealing. This idea got me thinking about our many customers in the beauty and fashion industry.

We’re thrilled to announce the launch of OnPage’s new Multiple Account Login feature. Designed to simplify critical communication workflows and safeguard data security for users working across multiple organizations, this functionality allows them to switch effortlessly between OnPage accounts without the need for repeated logins. Each OnPage account remains securely independent, ensuring that communication is organization-specific and private.

At FireHydrant, we know that alert management is about more than just getting notifications to the right people — it’s about reducing stress and fatigue, balancing workloads, and empowering your team to respond with confidence. That’s why we’re excited to unveil Round Robin for Signals Escalation Policies, a feature designed to make alert escalations smarter, fairer, and more team-friendly by allowing you to automate the sequential assignment of new alerts.