<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Concept on PG Exporter</title>
		<link>https://exp.pgsty.com/categories/concept/</link>
		<description>Recent content in Concept on PG Exporter</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<atom:link href="https://exp.pgsty.com/categories/concept/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Introduction</title>
				<link>https://exp.pgsty.com/intro/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://exp.pgsty.com/intro/</guid>
				<description>&lt;p&gt;&lt;code&gt;pg_exporter&lt;/code&gt; turns PostgreSQL and pgBouncer runtime state into Prometheus metrics. Unlike an exporter with a fixed list of hard-coded queries, most of its metric surface is declared in YAML: a collector defines SQL, result columns, labels, metric types, eligibility rules, timeouts, and caching policy.&lt;/p&gt;&#xA;&lt;p&gt;That design gives operators two useful properties at once:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;a release ships with a broad, tested default metric set;&lt;/li&gt;&#xA;&lt;li&gt;local teams can add, remove, or specialize metrics without rebuilding the binary.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;the-data-path&#34;&gt;The Data Path&lt;/h2&gt;&#xA;&lt;p&gt;A normal scrape passes through six stages:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
