<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Metrics on Wirez</title><link>https://wirez.top/tags/metrics/</link><description>Recent content in Metrics on Wirez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 30 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wirez.top/tags/metrics/index.xml" rel="self" type="application/rss+xml"/><item><title>Native CloudWatch metrics fix Direct Connect blind spots</title><link>https://wirez.top/posts/native-cloudwatch-metrics-fix-direct-connect-blind-spots/</link><pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/native-cloudwatch-metrics-fix-direct-connect-blind-spots/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">AWS eliminated the need for custom API polling by launching three native &lt;strong>CloudWatch metrics&lt;/strong> on March 30, 2026. This update fundamentally shifts hybrid cloud observability by exposing &lt;strong>BGP session health&lt;/strong> and prefix counts directly within the monitoring console, rendering previous workarounds obsolete. Instead of relying on external scripts or on-premises tools to detect silent route withdrawals, engineers can now track &lt;strong>VirtualInterfaceBgpStatus&lt;/strong>, &lt;strong>VirtualInterfaceBgpPrefixesAccepted&lt;/strong>, and &lt;strong>VirtualInterfaceBgpPrefixesAdvertised&lt;/strong> natively.&lt;/p></description></item></channel></rss>