<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Grafana on Besterry — Linux &amp; DevOps Notes</title><link>https://besterry.com/tags/grafana/</link><description>Recent content in Grafana on Besterry — Linux &amp; DevOps Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 05 Oct 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://besterry.com/tags/grafana/index.xml" rel="self" type="application/rss+xml"/><item><title>Grafana Dashboards That Don't Suck: Principles and Anti-Patterns</title><link>https://besterry.com/posts/grafana-dashboards-dont-suck/</link><pubDate>Sat, 05 Oct 2024 00:00:00 +0000</pubDate><guid>https://besterry.com/posts/grafana-dashboards-dont-suck/</guid><description>&lt;p&gt;Most Grafana dashboards are bad. Too many panels, unclear queries, inconsistent color schemes, no clear purpose. Here are the principles I apply now.&lt;/p&gt;
&lt;h2 id="rule-1-every-dashboard-has-one-question"&gt;Rule 1: Every dashboard has one question&lt;/h2&gt;
&lt;p&gt;Start by writing down: &amp;ldquo;What question does this dashboard answer?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Good:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Is the order service healthy right now?&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;How is the nightly ETL job progressing?&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;What is the cost trend for our compute in the last 30 days?&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Bad:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Production metrics&amp;rdquo;&lt;/li&gt;
&lt;li&gt;&amp;ldquo;Database overview&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you can&amp;rsquo;t state the question in one sentence, you don&amp;rsquo;t know what the dashboard is for.&lt;/p&gt;</description></item></channel></rss>