<?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>Sql on Ruben Meza</title>
    <link>https://soyunpollo.dev/tags/sql/</link>
    <description>Recent content in Sql on Ruben Meza</description>
    <generator>Hugo -- 0.158.0</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 20 Nov 2025 16:47:37 -0600</lastBuildDate>
    <atom:link href="https://soyunpollo.dev/tags/sql/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Monitoring Database Connection Pools in Grafana</title>
      <link>https://soyunpollo.dev/posts/db-sql-metrics-grafana-guide/</link>
      <pubDate>Thu, 20 Nov 2025 16:47:37 -0600</pubDate>
      <guid>https://soyunpollo.dev/posts/db-sql-metrics-grafana-guide/</guid>
      <description>&lt;p&gt;&lt;em&gt;Practical Guidance for Engineers Using Prometheus + Go’s &lt;code&gt;database/sql&lt;/code&gt; Metrics&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Most application performance issues in database-backed systems aren’t caused by MySQL itself — they come from &lt;strong&gt;connection pool pressure&lt;/strong&gt;, &lt;strong&gt;slow acquisition&lt;/strong&gt;, or &lt;strong&gt;misconfigured limits&lt;/strong&gt;.&lt;br&gt;
This post is a practical guide to understanding the key Prometheus &lt;strong&gt;&lt;code&gt;db_sql_*&lt;/code&gt;&lt;/strong&gt; metrics, why they matter, and how to visualize them effectively in Grafana.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;1-what-are-db_sql_-metrics&#34;&gt;1. What Are &lt;code&gt;db_sql_*&lt;/code&gt; Metrics?&lt;/h2&gt;
&lt;p&gt;When using Go’s &lt;code&gt;database/sql&lt;/code&gt; along with Prometheus instrumentation, your service emits a standardized set of metrics that describe your &lt;em&gt;client-side&lt;/em&gt; connection pool behavior.&lt;br&gt;
These cover:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
