> ## Content Index > Fetch the complete content index at: https://www.mohammadsiddiqui.com/llms.txt > Use this file to discover other available public pages before exploring further. # Eleven Management Packs in One Day: What VCF Operations Just Became - URL: https://www.mohammadsiddiqui.com/eleven-management-packs-in-one-day-what-vcf-operations-just-became/ - Published: 2026-09-03T10:47:31.000Z - Updated: 2026-09-19T04:52:24.000Z - Description: Five of the eleven are databases. That isn't a coincidence, and neither is the timing. What shipped, what changed underneath it, and the licensing detail that decides whether you can use any of it. - Author: Mohammad Siddiqui - Tags: Newsletter, operations On 3 September 2026, the same day VCF 9.1.1.0 shipped, eleven VCF Management Packs reached general availability at version 9.1.1.0. Eleven at once is unusual. Management packs normally trickle out on their own schedules. A simultaneous release of that size usually means something changed underneath them all, and in this case something did. 11 MANAGEMENT PACKS 5 ARE DATABASES 1 RELEASE DAY 9.1.1 3 SEP 2026 ## First, what a management pack actually is If you have only ever used VCF Operations for vSphere, vSAN and NSX monitoring, management packs are the mechanism that extends it to everything else. A management pack is distributed as a PAK file and installed through the VCF Operations interface: log in with administrator privileges, go to Repository, upload the PAK, accept the licence agreement, install. Once installed, you configure an adapter instance pointing at the target system with credentials, and the pack begins discovering objects, collecting metrics, and populating its dashboards and alert definitions. What you get from a well-built pack is four things: object discovery and a topology model of the target system, metrics and properties collected on a schedule, out-of-the-box dashboards, and alert definitions with symptom and recommendation logic already written by people who know the product. That last part is the actual value. Anyone can scrape metrics. Knowing which combination of metrics constitutes a problem worth waking someone for is domain knowledge, and it is what you are buying. THE VCF ARCHITECT FIELD GUIDE HOW A MANAGEMENT PACK COLLECTSTARGET SYSTEMSOracle / SQL / PostgresNetwork devices (SNMP)Kubernetes clustersServiceNowADAPTERcredentialsdiscoverycollection intervalobject modelVCF OPERATIONSmetrics + propertieslog contenttopology modelDashboardsAlerts + symptomsRecommendationsServiceNow incidentdetection becomes actionPAK file installed via VCF Operations → Repository. One adapter instance configured per target system. How a management pack collects: target system, adapter, VCF Operations, output. ## The eleven *Click any group below to expand.* Databases \- five of the eleven Five database packs in one release is a statement of intent, and it lines up with the Data Services Manager push. The database layer has historically been where infrastructure monitoring stops and someone else's tooling starts. The DBA team has its own console, the platform team has VCF Operations, and when a database performance problem turns out to be a storage latency problem, the two teams spend a morning comparing screenshots. - Microsoft SQL Server - [marketplace](https://vcf.broadcom.com/vsc/services/details/vmware-cloud-foundation-management-pack-for-microsoft-sql-server-1?slug=true&ref=mohammadsiddiqui.com) - Oracle Database - [marketplace](https://vcf.broadcom.com/vsc/services/details/vmware-cloud-foundation-management-pack-for-oracle-database-1?slug=true&ref=mohammadsiddiqui.com) - PostgreSQL - [marketplace](https://vcf.broadcom.com/vsc/services/details/vmware-cloud-foundation-management-pack-for-postgresql-1?slug=true&ref=mohammadsiddiqui.com) - MySQL - [marketplace](https://vcf.broadcom.com/vsc/services/details/vmware-cloud-foundation-management-pack-for-mysql-1?slug=true&ref=mohammadsiddiqui.com) - MongoDB - [marketplace](https://vcf.broadcom.com/vsc/services/details/vmware-cloud-foundation-management-pack-for-mongodb-1?slug=true&ref=mohammadsiddiqui.com) Infrastructure reach \- two These do different jobs. Network Devices targets network hardware with a device-aware object model. SNMP is the generic escape hatch for anything that speaks SNMP but will never get a purpose-built pack - appliances, environmental sensors, UPS systems. - Network Devices - [marketplace](https://vcf.broadcom.com/vsc/services/details/vmware-cloud-foundation-management-pack-for-network-devices-2?slug=true&ref=mohammadsiddiqui.com) - SNMP - [marketplace](https://vcf.broadcom.com/vsc/services/details/vrealize-operations-management-pack-for-snmp-3-2-1-11?slug=true&ref=mohammadsiddiqui.com) Platform and integration \- three ServiceNow is operationally the most consequential of the eleven. An alert on a dashboard is information. An alert that files a correctly categorised incident with the right assignment group is a process. - ServiceNow, the ITSM bridge - [marketplace](https://vcf.broadcom.com/vsc/services/details/vmware-cloud-foundation-management-pack-for-servicenow-1?slug=true&ref=mohammadsiddiqui.com) - Orchestrator, the path from detection to automated remediation - [marketplace](https://vcf.broadcom.com/vsc/services/details/vmware-cloud-foundation-management-pack-for-orchestrator-1?slug=true&ref=mohammadsiddiqui.com) - Aggregator, consolidating across multiple VCF Operations instances - [marketplace](https://vcf.broadcom.com/vsc/services/details/vmware-aria-operations-aggregator-management-pack-2-1-1?slug=true&ref=mohammadsiddiqui.com) Containers \- one VCF 9.1 already includes out-of-the-box monitoring and log management for VKS clusters natively. This pack is the broader Kubernetes story, for the clusters that are not VKS, which most enterprises have somewhere whether or not they appear on the architecture diagram. - Kubernetes - [marketplace](https://vcf.broadcom.com/vsc/services/details/vmware-cloud-foundation-management-pack-for-kubernetes-1?slug=true&ref=mohammadsiddiqui.com) ## What changed underneath all eleven This is the reason for the simultaneous release, and it is in the VCF Operations for Integrations 9.1 release notes rather than in any individual pack. Before 9.1.1 - two products, two content libraries Metrics lived in VCF Operations and came from management packs. Logs lived in Log Insight and came from content packs. Two products, two content libraries, and two places to look during an incident. From 9.1.1 - one pack carries both Log Insight is natively converged into VCF Operations, so a management pack ships metric content and log content as one artefact. A database pack does not just tell you the buffer cache hit ratio dropped - it surfaces the error entries from the same window, in the same interface. **That is why eleven packs shipped together. Every one was rebuilt to carry both.** THE VCF ARCHITECT FIELD GUIDE WHY ELEVEN PACKS SHIPPED TOGETHERBEFOREManagement Packmetrics only→ VCF OperationsContent Packlogs only→ Log Insighttwo products · two content libraries · two places to lookconvergence9.1.1One Management Packmetricslog contentone artefact · one console · same incident windowLog Insight is now nativelyconverged into VCF Operations.Every pack was rebuilt to carry both.That is why they shipped as a set.Legacy content packs can be convertedfor unified operational visibility.Also new: DSM-provisioned databasesmonitored with zero manual configuration,in a central Data Services view. Why eleven packs shipped together: metrics and logs converge into one artefact. The release notes also mention converting legacy content packs for unified operational visibility, which matters if you have built custom Log Insight content over the years. The second change in that release: databases provisioned through Data Services Manager get automated monitoring with zero manual configuration, surfaced in a centralised Data Services view covering PostgreSQL and MySQL, filterable at organisation, region, namespace or project level. Zero manual configuration is the operative phrase. If a tenant self-provisions a database through the catalogue, it appears in monitoring without anyone raising a ticket. Self-service that does not extend to observability just moves the ticket queue somewhere less visible. ## The licensing detail that decides whether any of this applies to you Broadcom's published feature comparison for VCF 9.1 and VVF 9.1 draws a line that is easy to miss and expensive to discover late. Capability vSphere Foundation VCF Edge VCF Infrastructure management packs SDDC, compute, storage, network, containers ✓ ✓ ✓ Application and management packs databases, middleware, app management ✗ ✓ ✓ Application monitoring Telegraf agent ✗ ✓ ✓ Prometheus Management Pack Builder PromQL API ✗ ✓ ✓ *Source: Broadcom, VCF 9.1 and VVF 9.1 Feature Comparison and Upgrade Paths* If you run vSphere Foundation, the database packs are not in scope Application packs require VCF or VCF Edge. That is a genuine reason to revisit edition selection if database visibility is your main operational gap, and it is exactly the kind of thing that surfaces in month three of a deployment rather than during design. ## Your move Tick these off as you read. Nothing is stored, it is just for your own pass through the list. Audit what your database team currently pays for monitoring. Five engines are now covered by packs included in a platform you may already run. Install the ServiceNow pack first if you run ServiceNow. It turns VCF Operations from a dashboard people check into a system that files work. If you are on VVF and the database packs matter, price the edition difference against your existing database monitoring tooling. Review legacy Log Insight content packs you built in-house. They can be converted, and unconverted custom content is a slow loss of institutional knowledge. Use the SNMP pack as your catch-all before commissioning custom integration work. If DSM is in your plans, note the monitoring comes with it. That changes the DSM business case slightly. ## Where this fits Step back and the direction is consistent with everything else in the 9.1 line. VCF Operations is being positioned as the single operational console for the whole estate, not just the virtual infrastructure layer. Metrics and logs in one place. Infrastructure, databases, network hardware, containers and ITSM in one object model. AI-ready APIs for exporting into RAG pipelines and MCP frameworks for anyone building on top of it. Whether it displaces your existing monitoring stack is a different question, and for most large estates the honest answer is partly. But the database packs are worth a serious look, because database monitoring is one of the few areas where the tooling is genuinely expensive and the integration with infrastructure context is genuinely poor. ## Sources - [VCF Operations for Integrations 9.1 Release Notes](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-1/release-notes/async-releases/vcf-operations-for-integrations-91-release-notes.html?ref=mohammadsiddiqui.com) \- DSM monitoring, log-based content in management packs - [VCF 9.1 and VVF 9.1 Feature Comparison and Upgrade Paths](https://www.vmware.com/docs/vmware-cloud-foundation-9-1-feature-comparison-and-upgrade-paths?ref=mohammadsiddiqui.com) \- edition availability - [Scale, Simplify and Secure Your Private Cloud Operations with VCF 9.1](https://blogs.vmware.com/cloud-foundation/2026/05/05/scale-simplify-and-secure-your-private-cloud-operations-with-vcf-9-1/?ref=mohammadsiddiqui.com) \- Prometheus pack, AI-ready APIs, VKS monitoring - [Operations in VMware Cloud Foundation 9.0](https://blogs.vmware.com/cloud-foundation/2025/06/17/modern-infrastructure-operations-vcf-9-0/?ref=mohammadsiddiqui.com) \- Management Pack Builder - [VCF Marketplace](https://vcf.broadcom.com/vsc/?ref=mohammadsiddiqui.com) *Views expressed here are my own and do not represent those of my employer.*