Grafana Faro and xk6-browser are both new tools within the Grafana Labs open source ecosystem, but the pairing is already showing a lot of potential in terms of frontend monitoring and performance testing. Faro, which was announced last November, includes a highly configurable SDK that instruments web apps to capture observability signals that can then be correlated with backend and infrastructure data.
I’ve always been wary about vendor events. In my experience, many of them are mostly marketing pitches, with little or no content that is applicable to my use cases. Despite that, last year I decided to convince my manager to let me attend ObservabilityCON 2022 to see what I could learn from it. My hope was that I would be able to get practical knowledge that could be applied as soon as I got back to work. (Spoiler alert: I did!)
Flaky tests are a problem that are found in almost every codebase. By definition, a flaky test is a test that both succeeds and fails without any changes to the code. For example, a flaky test may pass when someone runs it locally, but then fails on continuous integration (CI). Another example is that a flaky test may pass on CI, but when someone pushes a commit that hasn’t touched anything related to the flaky test, the test then fails.
At Grafana Labs, we love tracing, which is why we’ve been hard at work on Grafana Tempo, an open source, highly scalable distributed tracing backend. Tempo just had its 2.0 release. In conjunction with that release, we are excited to show off TraceQL — a powerful new query language designed for distributed tracing. In this blog, we’ll provide an overview of why we created TraceQL, how it works, how you can put it to use today, and what we have planned for future iterations.
We recently launched a new design for our technical documentation. The goal of the redesign was to make our technical documentation more accessible, modern, and scalable as we grow. In addition to a new look (hello, new typeface and layout!), our updated docs pages reveal the underlying work our team has done to evolve and enhance our technical documentation.
While more and more teams are adopting Kubernetes as their standard container orchestration technology, cost insight is lacking. Teams often don’t know how much they’re spending, where in their organization they are spending, or what is driving their infrastructure cost increases. OpenCost helps alleviate this problem by bringing real-time cost monitoring to Kubernetes workloads with a solution that encompasses both an open specification and an open source project.
Our latest open-source project, Helm-Dashboard, just crossed 3K stars on GitHub (and hundreds of daily active users), only three months since it was released! We thought this milestone was a good chance to take a look back at our journey, announce the release of v. 1.0.0, discuss future plans, and, most importantly, give our utmost thanks to the amazing contributors and Kommunity members that made it all possible! What capabilities would you like to see next in Helm-Dashbaord?
