Vcf-Operations

Telegraf runs the script every 60 s; the script's stdout is one integer; the integer is the health of the integration

vLLM metrics into VCF Operations, part 2: monitor the monitor

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.

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.

The same Cluster manifest applied by kubectl and requested through the catalog — and what the second path adds for free

One VKS cluster, two ways: kubectl vs VCF Automation All Apps

The same VKS cluster built twice: once with kubectl, once as a VCF Automation request. The Cluster object is identical. Everything around it isn’t, and the difference is what you get for free.