<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dbm on Netdata</title><link>https://www.netdata.cloud/tags/dbm/</link><description>Recent content in Dbm on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 24 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/dbm/index.xml" rel="self" type="application/rss+xml"/><item><title>Database Performance Monitoring: 14+ DBs Supported</title><link>https://www.netdata.cloud/blog/dbm/</link><pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/dbm/</guid><description>&lt;p>&lt;img src="../images/dbm-hero.svg" alt="Database Performance Monitoring: Query-Level Visibility Across 14+ Databases">&lt;/p>
&lt;p>Netdata has always collected database metrics: connections, throughput, replication lag, buffer cache hit ratios, and so on. These tell you that something is wrong, but they don&amp;rsquo;t tell you why. When your PostgreSQL response time spikes, the metric alone doesn&amp;rsquo;t tell you which query is responsible. For that, you&amp;rsquo;ve traditionally needed to SSH into the box, connect to the database, and run diagnostic queries manually. Or set up a separate database monitoring tool entirely.&lt;/p></description></item></channel></rss>