<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Google Secret Manager on Netdata</title><link>https://www.netdata.cloud/tags/google-secret-manager/</link><description>Recent content in Google Secret Manager on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 22 Aug 2026 05:09:03 +0300</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/google-secret-manager/index.xml" rel="self" type="application/rss+xml"/><item><title>Secrets Management: Remove Credentials From Configs</title><link>https://www.netdata.cloud/blog/secrets-management/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/secrets-management/</guid><description>&lt;p&gt;If you&amp;rsquo;re running Netdata collectors that connect to databases, APIs, or other authenticated services, there&amp;rsquo;s a good chance you have passwords sitting in plain-text configuration files right now. It works, but it&amp;rsquo;s the kind of thing that makes security teams nervous and makes credential rotation painful. Every password change means editing config files and restarting collectors.&lt;/p&gt;&#10;&lt;p&gt;Netdata now supports secrets management natively. Instead of putting credentials directly in your collector configurations, you reference them using a resolver syntax, and Netdata resolves the actual values at runtime from whatever source you choose: environment variables, files on disk, the output of a command, or a centralized secret store like HashiCorp Vault or AWS Secrets Manager.&lt;/p&gt;</description></item></channel></rss>