Last week, we were very excited to host our first ever SquaredUp Virtual Customer Workshop! We’d received so much positive feedback on the intimate in-person workshop we ran in the UK last month that we wanted to extend the invitation worldwide – by recreating the experience virtually. Using the digital conferencing app Gather Town, we were pleased to welcome 23 SquaredUp customers from 12 countries to our virtual “SquaredUp Town”.
Grafana is an open-source web application for visualizing data. You can query your data, create visuals, and receive alerts to better understand what you have. Some people think of Grafana as a Kubernetes-only tool, but in reality, it’s simply a data visualization tool that became popular within the Kubernetes ecosystem, especially when combined with Prometheus. In this post, I’ll focus on a very specific part of Grafana: the dashboards.
Since we introduced role-based access control (RBAC) in Grafana 9.0, users — and later, service accounts — have been required to have an assigned role that includes a basic set of permissions. This sometimes led organizations to create users and service accounts that had more permissions than necessary. As a result, Grafana administrators had to make additional adjustments to users’ permissions on a case-by-case basis.
When it comes to observability, we’ve found that most organizations have ~20 tools installed in their IT environments. With so many tools, it’s difficult for IT leaders to gain insight into how their tools are performing and determine how much value ITOps is bringing to the organization.
When you use OpenTelemetry SDKs to collect logs, metrics, and traces from infrastructure or an application, you’ll find many references to people using Grafana Agent and OpenTelemetry Collector. They start with an application or infrastructure that sends telemetry, and that data is sent to a collector, which then sends it to a backend like Grafana that may perform many functions, including visualization.
Unlocking the full potential of observability and tracing in modern software ecosystems has become imperative for businesses striving to deliver improved reliability and user experience. In this comprehensive roundup, we will dive into the world of Jaeger-incorporated observability and tracing dashboards, offering a curated selection of the best use cases that empower DevOps teams, engineers, and developers to gain unparalleled insights into the inner workings of their applications.
Observability isn’t just about watching for errors or monitoring for basic health signals. Instead, it goes deeper so you can understand the “why” behind the behaviors within your system. CI/CD observability plays a key part in that. It’s about gaining an in-depth view of the entire pipeline of your continuous integration and deployment systems — looking at every code check-in, every test, every build, and every deployment.
