<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud-Logging on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/cloud-logging/</link><description>Recent content in Cloud-Logging on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 28 Sep 2026 18:19:45 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/cloud-logging/index.xml" rel="self" type="application/rss+xml"/><item><title>GCP: Legacy Monitoring agent EOL and Cloud Logging billing account restriction</title><link>https://curadevops.metacog.co.kr/insights/2026-09-28-september-28-2026/</link><pubDate>Mon, 28 Sep 2026 18:19:45 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-28-september-28-2026/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Act:&lt;/strong> The GCP Legacy Monitoring agent has officially reached end of support with all maintenance and bug fixes ceased; audit GCP VM instances for legacy agent usage and migrate to Ops Agent or OpenTelemetry now. A breaking Cloud Logging change also restricts billing account log writes to GCP platform services only — audit any custom logging pipelines writing to billingAccounts/…/logs/… paths and update them.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> deprecation mentioned (no explicit date found)&lt;/li>
&lt;/ul></description></item></channel></rss>