{"id":14323,"date":"2026-07-15T13:02:05","date_gmt":"2026-07-15T11:02:05","guid":{"rendered":"https:\/\/irg-net.com\/?p=14323"},"modified":"2026-07-15T14:18:44","modified_gmt":"2026-07-15T12:18:44","slug":"deploying-activating-vcf-log-management-in-vcf-9-1-0-400","status":"publish","type":"post","link":"https:\/\/irg-net.com\/index.php\/deploying-activating-vcf-log-management-in-vcf-9-1-0-400\/","title":{"rendered":"Deploying\/Activating VCF Log Management in VCF 9.1.0.400+"},"content":{"rendered":"
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n

Since VCF 9.1.0.x, a lot has changed in the platform \u2014 and one of the more noticeable shifts is how Log Management works. It is no longer a standalone virtual appliance you deploy and patch on its own. Instead, it now runs as a service inside the VCF Management Services Cluster, the same Kubernetes-based runtime that also hosts Fleet Management and the other core management components.<\/p>\n\n\n\n

In this post I’ll walk through how to deploy VCF Log Management in 9.1.0.x, which is relevant for both VCF and VVF customers.<\/p>\n\n\n\n

<\/div>\n\n\n\n

What Changed<\/h3>\n\n\n\n

In VCF 9.0 and earlier, Log Management (formerly Aria Operations for Logs) was deployed as its own appliance VM or appliance cluster. From 9.1 onward, it is a built-in, containerized core service that runs natively on the VCF Management Services Platform. Deployment, lifecycle management, configuration, access control, and alerting are now all handled centrally through VCF Operations, rather than through a separate product UI.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Prerequisites<\/h3>\n\n\n\n