Like many in the observability space, we see a lot of potential in harnessing AI to enhance the developer experience. As we continue to evolve and expand our observability platform, we strive to develop features that not only solve complex problems, but make it easier to access and derive value from tools like Grafana Pyroscope.

One of the superpowers of Grafana is the ability to bring all of your data into a single platform thanks to our rich catalog of data sources. Oftentimes you will want to visualize information from disparate data sources together in a single dashboard or panel. Or you might want to refine data returned from queries without altering the original data source. Or you may need to modify data due to limitations of a query language that stops you from getting the required formatting.

The maturity of your alerting strategy has a direct impact on the reliability of your infrastructure and your applications. It can also have a big impact on engineering productivity. So whether you’re talking about resolving incidents faster or avoiding alerting fatigue, alerting should always be front and center.

At GrafanaCON 2024, Grafana founder Torkel Ödegaard introduced Grafana 11, which has a feature set that aligns with the same goals we’ve had since the OSS project launched in 2013. “The core mission of Grafana that we’ve had from the start is to make observability easy and powerful through good UX design, a focus on ease of use, and user flexibility and freedom,” Torkel said.

One of the most powerful features of Grafana is the ability to unify and derive value from your data, regardless of where that data lives. This is because we’re fully committed to making Grafana an open, composable, and extensible observability platform for our more than 20 million users worldwide. But how exactly do we deliver on that promise of openness and extensibility? Grafana data source plugins play a big role.

Are you using the Azure metrics exporter to ship telemetry data to Grafana Cloud? Are you overwhelmed with the amount of configuration and complexity necessary to avoid being rate limited? Well, did you know that with Grafana Alloy, our distribution of the OpenTelemetry Collector with built-in Prometheus pipelines and support for metrics, logs, traces, and profiles, you can now: Let’s look at how these two features can reduce the complexity of your Alloy configuration.

AWS is an essential part of many organizations’ tech stacks today, which is why we continue to make it easier to observe your environment in Grafana Cloud. We recently launched AWS Observability, a fully managed application for visualizing and alerting on dozens of AWS offerings. And with our latest update, we’re making it cheaper and simpler to ingest and query your AWS logs.

At Grafana Labs, we’re committed to helping teams dramatically improve how they manage and respond to incidents. Through Grafana Incident Response & Management (IRM), we provide tools to empower teams, streamline processes, and enhance the effectiveness of incident management strategies—and we’re constantly looking for ways to make our solution even better.

Recently, an incorrect security report was published, claiming that there’s a SQL injection attack in Grafana. As we have communicated to the security researcher, this report is wrong. Authenticated users in Grafana have the same permissions as the user configured for the underlying data source.

Editor’s note: This blog post is the second in a series of posts about organizing your performance testing suite with Grafana k6. If you haven’t already, be sure to check out the first post in the series, which explores how to implement reusable test patterns and other best practices within your testing suite.