Observability on VCF

Getting logs and metrics out of the places that don’t come with an adapter (VKS clusters, Windows Server 2025, a stubborn agent or two) and into VCF Operations and Operations for Logs. Real configs, real traps, and what to check when a dashboard stays empty. Start with fluent-bit two ways.

Telegraf pods stuck in FailedMount until the Supervisor Management Proxy exists; then a domainless service URL until serviceDomain is set

Telegraf on VKS: the dependency that isn't in the README

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 support matrix says no; the agent status says Install Success

Telegraf on Windows Server 2025: unsupported, works anyway

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.

Two fluent-bit shippers — a VKS package and a Windows service — converging on one Ops for Logs endpoint

fluent-bit two ways: VKS add-on and Windows agent, one log endpoint

One log pipeline, two very different worlds: fluent-bit as a VKS package and as a Windows Server 2025 service, both shipping to the same VCF Operations for Logs. One backend, two configs, lessons from both.