Operations | Monitoring | ITSM | DevOps | Cloud

There are a common set of key performance indicators for incident management, such as MTTR and MTTA. What do these metrics mean, and why are they important?

This blog is about how to communicate changes in your application monitoring process as your operations, environments and services evolve. Approaching your operations with a “monitoring as code” mindset - which means automating as much of the entire observability lifecycle, including automated diagnosis, alerting and incident management, and even automated remediation - is foundational to the success of your operational technology.

I’m a bit late to the game in writing about observability, but I come with a great excuse: since March, I’ve travelled the world (well, at least four out of the seven continents) to discuss this observability thing with our Partners. Later, as we were able to disclose more details, we discussed it with customers, too. A lot’s happened in the past four months.

When Grafana started in 2014, its main goal was to be a great dashboarding solution for Graphite. Around the same time, the Prometheus project started to gain steam, but it wasn’t clear whether it should be added to Grafana. After all, Grafana was a Graphite frontend, it was uncertain at the time if Prometheus would take off in popularity, and it would take resources away from the core purpose of why Grafana was created.

Load balancers and content delivery networks (CDNs) are critical tools for delivering modern, cloud-native applications. They play essential roles in ensuring the smooth flow of data between applications and end-users. If you don’t have both a load balancer and a CDN in place, you’re probably in a poor position to guarantee the uptime of your application across a wide geographic area. That does not mean, however, that load balancers and CDNs do the same thing.

Although we’ve encouraged employees to take plenty of time off this summer to relax, recharge, and enjoy time with family, Cribl certainly hasn’t been on a summer holiday as a company. After the big announcement in late May with Cribl Search and our Series D funding round, we moved right into the announcement of Cribl Stream 3.5, Cribl Edge 3.5, massive upgrades to Cribl.Cloud, and the launch of our Cribl Certified Observability Program.

We are back with a simplified configuration for another critical open-source component, Hadoop. Monitoring Hadoop applications helps to ensure that the data sets are distributed as expected across the cluster. Although Hadoop is considered to be very resilient to network mishaps, monitoring Hadoop clusters is inevitable. Hadoop is monitored using the JMX receiver. The configuration detailed in this post uses observIQ’s distribution of the OpenTelemetry collector.

Written by Nick Cavalancia, Technical Evangelist, Microsoft MVP, & CEO of Conversational Geek In a world of Managed IT Service Providers that all offer some form of services around Microsoft 365, there’s a compelling case to be made for your business to be centering in on Microsoft Teams.

Recently we caught up with the Sumo Logic team to discuss network visibility and optimizing application stack views. We took a look at their API and found that it would be easiest to use the HTTP Ingest method to send in our metric data.

Google has a well earned reputation for speed. At least on their own sites. It’s an entirely different story when it comes to their ad network. Google ads are slowing down thousands of sites across the internet.