Once you have set up your Prometheus data sources in Grafana, it’s time to put them to work. In the one-minute tutorial video below, we show you how to build a query in Grafana 8.3 with Grafana’s easy-to-use Explore mode. Prometheus uses a query language called PromQL. If you are already familiar with PromQL, you can simply enter your query in the text field and run the query.
Grafana Tempo 1.3 has been released! We are proud to add the capability to search the backend datastore. This feature will also appear soon in Grafana Cloud Traces. If you want to dig through the nitty-gritty details, you can always check out the v1.3 changelog. If that’s too much, this post will cover the big ticket items. You can also register for our upcoming webinar “Distributed tracing in Grafana: From Tempo OSS to Enterprise” on Jan.
Beep, beep, beeeeeeeep. Read path SLO page, again. And I’ve almost found the noisy neighbor! That was me. And will probably be me again at some point in the future. As we continue to scale up the team that builds and runs Grafana Loki at Grafana Labs, I’ve decided to record how I find and diagnose problems in Loki.
Networks are the backbone of inter-communications within computer systems and applications. When networks go down or experience any interruption of service, the impact is widely felt and can result in significant service disruptions and lost revenue. This is why network monitoring is mission critical for organizations. Visibility into network performance is key to ensuring that network engineering teams can be more proactive and identify problems before those issues cause outages.
After the success of our first company-wide hackathon last June, we committed to hosting more hackathons each year. So in December, Grafana Labs invited the company to once again press pause on the daily grind and commit five days to our second hackathon. And the Grafanistas showed up: 148 staffers (almost 20% more than the last round) signed on for the week-long event that involved virtual brainstorming, collaborative coding, and creative presentations.
It was a Wednesday in November, and we had just wrapped Grafana Labs' third virtual Grafana Cloud offsite of 2021. Outside my window, it was a dark and cold (8 degrees Celsius) night in Cologne (Köln), Germany. In Austin, Texas, it was early afternoon and headed for 80 degrees Fahrenheit. In Cape Town, South Africa, it was a windy and cool spring evening. And in Melbourne, Australia, our final speaker — who was up very early at 5 a.m. — was heading into a cool spring day.
Anders Østhus is a DevOps Engineer on the Digital Tools team at Proactima AS, a consulting firm based in Norway that offers services and expertise in risk management, cybersecurity, healthcare, environmental solutions, and more. It can be difficult to orient yourself in the distributed tracing space, and getting all the parts of a tracing setup to play well with each other can be a bit tricky. But the benefits of tracing are undeniable.
We often hear from Grafana Cloud users who are asking for guidelines on how to write better alerts on synthetic monitoring metrics and get notified when synthetic monitoring detects a problem. We already ship a predefined alert in Grafana Cloud synthetic monitoring. A predefined alert that we ship is alerting on the probe_all_success_sum metric and makes use of the alert sensitivity config to create multiple Grafana Cloud alerting rules. Check out synthetic monitoring alerting docs for details.
