{"id":2322,"date":"2025-12-16T16:01:54","date_gmt":"2025-12-16T15:01:54","guid":{"rendered":"https:\/\/thomas-kopton.de\/vblog\/?p=2322"},"modified":"2025-12-16T16:01:56","modified_gmt":"2025-12-16T15:01:56","slug":"migrating-content-and-config-from-aria-operations-for-logs-8-18-to-vcf-operations-for-logs-9","status":"publish","type":"post","link":"https:\/\/thomas-kopton.de\/vblog\/?p=2322","title":{"rendered":"Migrating Content and Config from Aria Operations for Logs 8.18 to VCF Operations for Logs 9"},"content":{"rendered":"\n

Introduction<\/strong><\/h4>\n\n\n\n

As organizations modernize their Private Clouds with VMware Cloud Foundation 9<\/mark><\/strong>, the logging infrastructure undergoes a significant evolution. Transitioning from VMware Aria Operations for Logs 8.18.x<\/strong> <\/mark>(formerly vRealize Log Insight) to the new VCF Operations for Logs 9<\/mark><\/strong> is designed as a side-by-side migration requiring a fresh deployment.<\/p>\n\n\n\n

While there is a fully supported method to transfer up to 90 days of historical log data to the new instance, ensuring operational continuity requires a strategy for your custom logic. Beyond just log data, your environment relies on years of tailored content\u2014such as Dashboards, Alert Definitions, and Extracted Fields\u2014as well as specific configuration settings<\/strong> that tune the system to your environment.<\/p>\n\n\n\n

Since these artifacts are not automatically carried over during the deployment, preserving them requires a targeted approach. In this post, I will outline how to leverage the native tools and features within Aria Operations for Logs and VCF Operations for Logs 9 to effectively migrate your critical content and essential configuration settings to the new VCF 9 platform.<\/p>\n\n\n\n

Content Export using Custom Content Packs<\/strong><\/h4>\n\n\n\n

One of the most efficient ways to migrate bulk content is to treat your custom work as if it were a third-party application. In Aria Operations for Logs<\/strong>, Content Packs<\/strong> are essentially containers designed to package logic and visualizations for portability. While we typically associate them with vendors (e.g., the vSphere Content Pack<\/em>), you can create your own private Content Packs to bundle your environment’s custom artifacts into a single, portable .vlcp<\/code> file.<\/p>\n\n\n\n

This method is ideal because it maintains the relationships between objects. for example, if you add a Dashboard to a Content Pack, the system is generally smart enough to prompt you to include the dependencies (like the Queries or Widgets used in that Dashboard).<\/p>\n\n\n\n

What Can Be Included?<\/strong><\/h5>\n\n\n\n

When you create a custom Content Pack for migration, you can include the following objects:<\/p>\n\n\n\n