Operations | Monitoring | ITSM | DevOps | Cloud

This is going to be the first of at least two posts about how we, in the Mezmo platform team, use Pipeline to handle metrics. It’s an ongoing effort and everything might change as we move forward and learn, but this is our plan and vision.

Are you searching for a reliable StatusGator alternative? Welcome to IsDown, your premier choice for status page aggregation! Unlike simply comparing features, we invite you to experience the distinct advantages of IsDown firsthand, tailored to your unique requirements.

During the early periods of cloud computing, most organizations used single-location data centers. These single-location data centers often faced higher risks of downtime and service disruption due to localized disasters or hardware failures. As a solution to these problems, cloud services like AWS introduced the concept of availability zones. This introduction was an important milestone in the evolution of cloud computing, as it facilitated high availability through geographic distribution.

In our webinar, Mastering Telemetry Pipelines: A DevOps Lifecycle Approach to Data Management, hosted by Mezmo’s Bill Balnave, VP of Technical Services, and Bill Meyer, Principal Solutions Engineer, we showcased a unique data-engineering approach to telemetry data management that comprises three phases: Understand, Optimize, and Respond.