Part 1’s design only helps if it runs every minute, for ever, and says when it stops. Self-monitoring through Telegraf, batched pushes, the four alerts for day one, and an offline test mode.
On VCF 9.1, the supported route installs Telegraf in new VKS clusters for you. Underneath sits a dependency the README never mentions, two secrets from the Supervisor Management Proxy, and without them every Telegraf pod is stuck.
The VCF Operations agent matrix doesn’t list Windows Server 2025. Add one missing Windows component, WMIC, and the normal install just works. What ‘unsupported’ really means, and what to watch.