Apache Cassandra is a highly scalable, open source NoSQL database system designed to handle large amounts of data across multiple commodity servers with no single point of failure. Apache Cassandra can be run as a single node but starts making sense when its run in a cluster setup. The system is optimized for high write throughput and is known for its ability to handle big data workloads with ease at super-low latencies.

As more organizations adopt cloud-based services like Microsoft Azure Kubernetes Service (AKS), it becomes increasingly important to monitor and manage the performance and reliability of these services. If you’re using AKS today, then Grafana Cloud provides the flexibility, performance, and visualizations you need to monitor your distributed applications.

Grafana Loki 2.8 is here — and it’s at least 0.1 better than Loki 2.7! Jokes aside, this release includes a number of improvements users will appreciate. In addition to graduating our TSDB index from Experimental to General Availability, we’ve added a number of nifty LogQL features, and we’ve made the Loki deployment and management experience much easier. This also marks the release of Grafana Enterprise Logs (GEL) 1.7.

We often see questions about how to template alerts. In Grafana, you can template information about your alerts with custom labels and annotations, and you can also template how notifications look and what information they contain with notification templates. Many users confuse the two, despite being separate features with different use cases.

As a developer, I’m always thinking about ways I can make my work on projects better, faster, and more organized. Over the years, I’ve learned that tracking development metrics is a really helpful way to do that.

There are many aspects of application performance, but they broadly fall into two categories: frontend performance and backend performance. As a tester, it’s important to know the differences between the two and how that impacts the way you approach your tests. In this blog, I’ll provide a high-level overview of frontend performance testing and backend performance testing, including pros and cons of each one.

Compliance is a term commonly associated with heavily regulated industries such as finance, healthcare, and telecommunication. But in reality, it touches nearly every business today as governments and other regulatory agencies seek to enact tighter controls over the use of our collective digital footprint. As a result, more and more companies need to retain a record of every single digital transaction under their control.

When we introduced Grafana Mimir into the open source ecosystem, we weren’t shy about our ambitions. Once we got past answering some of the easier questions (For the record, the name Mimir comes from Norse mythology, and it’s pronounced /mɪ’mir/.), we quickly got to work making good on our promise to deliver the most scalable, most performant open source time series database (TSDB) in the world.

What do you get when you combine the wit, wisdom, and weird humor of four talented tech minds? As it turns out, a surprisingly lively Q&A! As Grafana Pyroscope emerges from the union of Grafana Phlare and Pyroscope, it’s time to really get to know the people behind these continuous profiling projects. That’s why we brought together the Pyroscope founders, Dmitry Filimonov and Ryan Perry, and Phlare technical leads, Cyril Tovena and Christian Simon, for this light-hearted conversation.

Organizations use load and performance testing to prevent issues from impacting customers, which is essential if they want to stay relevant in today’s digital-first world. And with the rise of cloud native technology and DevOps, software teams must shift performance testing left, towards development. However, traditional load and performance testing tools simply haven’t kept pace, leaving developers, operations, and QA teams siloed.