Operations | Monitoring | ITSM | DevOps | Cloud

Usability and control are key elements in BigPanda’s Operations Console, where IT Ops, NOC and DevOps users investigate and take action on IT incidents. Let’s take a look at how BigPanda’s powerful Split Incident and Merge Incidents features provide IT Ops with an added layer of control. BigPanda’s Open Box Machine Learning correlates and enriches the overwhelming amount of alerts IT Ops needs to deal with into a reduced number of insight-rich incidents (often 95% fewer).

04 Jul 2019 Ryan Glass, lead developer at Downtime Monkey and director of Big Toe Web Design gives us the recipe for his ideal downtime alert setup... Yes! At Big Toe we use it for all our website monitoring. As well as building sites, we manage the hosting of our client's websites and we monitor these to make sure that they are up and running round the clock. That depends on the site/client.

As a website or web service provider, you live and die based on your KPIs (Key Performance Indicators). In this article, we define those KPIs and help you decide which tools you need to monitor and track the KPIs you care about.

Over the past few years, and coupled with the growing adoption of microservices, distributed tracing has emerged as one of the most commonly used monitoring and troubleshooting methodologies. New tracing tools and frameworks are increasingly being introduced, driving adoption even further. One of these tools is Jaeger, a popular open source tracing tool. This article explores the integration of Jaeger with the ELK Stack for analysis and visualization of traces.

A post-geographical culture means more than putting a face to the name. Here, the Grafana Labs team is also putting a photo to the workspace. Check out the setups that have been where some of the latest Grafana releases and products have been developed. What you’ll learn is that not only is the Grafana Labs team adept at creating dashboards, supporting hosted services, and hosting conferences.

Errors suck. And you don’t want to spend too much of your time fixing them, dealing with them, investigating them, etc. In our Workflow blog post series, we look at how to optimize your, well, workflow, from crash to resolution. At this point in our workflow (check out the first and second posts in this series), we’ve minimized the impact of errors on the development process by creating infrastructure and culture equipped to handle unexpected issues.