Operations | Monitoring | ITSM | DevOps | Cloud

Are you on DEV? Did you know that it's open-source, and that it uses Honeybadger? We just launched a new feature to help communities like DEV fix more errors together! Software development is more fun with friends; that's why we've built tons of collaboration features into Honeybadger over the years, making it easier for teams to fix errors. Recently the team at DEV emailed us with a feature request: could we make it easier to involve the broader DEV open source community in the error-fixing process?

At FOSDEM 2020, Grafana Labs software engineers Tom Braack and Malcolm Holmes explained how and why the team developed Tanka, a scalable Jsonnet-based tool for deploying and managing Kubernetes infrastructure. They also shared how Grafana Labs leverages the project to manage and monitor its own infrastructure as well as showcased how Tanka makes deploying a Grafana instance faster and more efficient.

You’re done setting up your first graph panels. You want to do more, look around the visualization settings, and discover the settings for the X and Y axes. You stumble over the configuration for a “Right Y” axis. You ask yourself, “Why on earth would I need another Y axis?” You toggle it back and forth and change some settings, yet that makes no difference to your graph. What gives? Never fear.

So far, we’ve learnt how to collect data (part 2) and pull it into Azure Log Analytics (part 3), as well as how to actually work with the data using Kusto (part 4). Now it’s time to explore how we can visualize this data, make dashboards, share them with other teams in our organizations and so on. Unfortunately, dashboarding in Azure is not very sophisticated, and neither is it centralized.

Certificates can be difficult to track and opaque to administrators, and if any expire without someone noticing, embarrassing outages can happen. At Grafana Labs we strive to make all things visible and observable; why should certificates be any exception? In this post we will explore an easy way to expose and monitor certificate expirations using Grafana and Prometheus.

While powerful, our first iteration of Discover had some user experience complexities that made it less user-friendly than other potential search mechanisms. We also heard from you that our Events feature was useful for identifying individual events, but finding common patterns within those events was extremely difficult — keyword, ”was”. I want to share some of the features and the top 5 use cases that you can do with the refreshed Discover.

If you haven’t yet heard...Splunk dashboards are new and improved! We released a new dashboard framework as a beta app at .conf19, and have been working hard to improve it since then. This blog post will cover the highest-impact features in the release. For notes on every feature, see the release notes on Splunkbase. To see a run-anywhere dashboard highlighting the key features from this release, copy the JSON definition from our Github.

There has long been a request from administrators to have the ability to enforce a minimum interval between alert rule evaluations. This is useful for restricting unrealistic user-defined alert rules that evaluate too often and create unnecessary load in the backend. @Uepoch took the initiative and made all the necessary modifications for this configuration in Grafana’s backend, and we finally pushed it forward and introduced the feature in Grafana v6.6.