<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Google-Cloud-Platform on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/google-cloud-platform/</link><description>Recent content in Google-Cloud-Platform on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 06 Aug 2026 12:51:55 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/google-cloud-platform/index.xml" rel="self" type="application/rss+xml"/><item><title>GCP: Telemetry API OTLP ingestion and Cloud SQL perf capture go GA</title><link>https://curadevops.metacog.co.kr/insights/2026-08-06-august-05-2026/</link><pubDate>Thu, 06 Aug 2026 12:51:55 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-06-august-05-2026/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Two GA releases are worth scheduling for adoption: native OTLP metric ingestion into Cloud Monitoring via the Telemetry API (evaluate replacing or supplementing existing collector pipelines), and Cloud SQL for MySQL performance capture with configurable thresholds for long-running transactions and new triggers like CPU, memory, and lock waits.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> The Telemetry API GA enables native OTLP ingestion into Cloud Monitoring, which may affect the build-vs-buy decision for third-party observability tooling on GCP; no strategic decision is required yet.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> GA announcement&lt;/li>
&lt;/ul></description></item></channel></rss>