VCF Operations

Prometheus histogram buckets in; flat P50/P95/P99 gauges out

vLLM metrics into VCF Operations, part 1: don't ship the histogram

vLLM exposes about 200 Prometheus series per model, and pushing them raw into VCF Operations is a cardinality bomb. A pipeline that computes the useful numbers client-side and drops what can’t be graphed.

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.