How to monitor after migrating from VMware to Hyper-V, Proxmox or hybrid environments

How to Keep Strong IT Monitoring After Leaving VMware

Few things are more unnerving than abandoning familiar ground—especially in technology. We knew our infrastructure and all its quirks like the back of our hand and everything “worked perfectly” (ahem). But VMware decided its prices should reach Mars before Elon Musk, and many organizations had to migrate to survive.

Regardless of the chosen alternative, this brings common challenges such as:

• Maintaining operational continuity with no loss in performance or efficiency.
• Retaining full visibility and control over the new infrastructure to ensure performance and key metrics like SLA (Service Level Agreement) remain stable—or even improve.

With Hyper-V or Proxmox VE, new opportunities arise: cost savings, flexibility and greater independence by reducing vendor lock-in (in theory). But let’s be honest—VMware has long been the benchmark in virtualization, and new solutions mean new challenges, from performance variations to management changes.

Especially at the beginning, transparency is crucial because without monitoring we cannot know whether migration is truly beneficial.

Let’s see how to achieve that, starting with Microsoft’s solution—focusing on virtualization, though Hyper-V and Proxmox also include features such as backup, networking or storage.

Scenario 1: Migration from VMware to Hyper-V

When moving away from VMware, the first decision is whether you are more comfortable in the Windows or Linux world.

Maybe your servers still carry those Windows stickers that never come off cleanly, or perhaps Microsoft’s enterprise-grade support makes Hyper-V the natural choice. In any case, some key changes will follow.

• Architecture: Hyper-V runs on Windows. It has been included in Windows Server since 2008. You don’t license Hyper-V separately—you license Windows Server.
• Monitoring: Choosing Pandora FMS lets you monitor your new environment through the Pandora FMS Hyper-V Monitoring Plugin.

Monitoring Hyper-V with Pandora FMS after migrating from VMware

The plugin includes many modules for metrics like CPU and memory usage, demand, packets, uptime, and more. Some modules come with predefined thresholds, but at Pandora we believe in “your system, your rules”, so everything is easily adjustable from Pandora FMS console.

Plugin installation is done under Configuration > Pandora Collections, allowing you to deploy it on multiple servers simultaneously if needed.

Once configured (see this configuration example and sample screenshots), the plugin reports data at regular intervals.

With everything running, you may define alerts, feed metrics into Pandora dashboards, and monitor virtualization from the “Resources” section.

Lessons Learned

• Reduced license costs by avoiding VMware’s new pricing model. Hyper-V follows a more rational approach. For instance, Windows Server Standard includes two VMs per license—if you need six VMs, you’ll require three Windows Server licenses covering all physical cores.
• Quick deployment if you’re familiar with Windows and the Hyper-V Console. The learning curve exists but remains short—within weeks you’ll feel comfortable. Also, Hyper-V includes native VMware migration features.
• Stable metrics since Pandora FMS monitoring provides a consistent, unified view alongside the rest of your IT KPIs.

But what if you’re not ready to join the Borg and let Microsoft assimilate you—swapping one walled garden for another?

A fair concern. We all know the habits of the Redmond giant, which might be watching how VMware’s pricing experiment turns out.

In that case, it’s time to join the Open-Source Rebel Alliance and choose Proxmox VE.

Scenario 2: Migration from VMware to Proxmox VE

If you wish to embrace Open Source and deploy Proxmox VE for free, you’ll need to close the Windows in your data center (pun intended) and move to Linux.

This doesn’t mean losing flexibility, since Proxmox VE—based on Debian—can virtualize other OSs through KVM. It also supports lightweight Linux virtualization through LXC containers.

That makes it an appealing choice: technically powerful and cost-efficient (no license fees). But nothing in life is completely free.

You’ll need to be familiar with Linux and time to learn Proxmox, which may feel too demanding for IT admins new to that ecosystem.

Proxmox’s business model relies on paid support (by subscribing to its Enterprise repository). Different packages exist, and you’ll need to gauge your operational needs.

Proxmox even provides an official VMware migration guide—and the best part is that monitoring with Pandora FMS after migration is straightforward.

Monitoring Proxmox with Pandora FMS after migrating from VMware

Once Proxmox VE is deployed and your VMs and features mirror what you had under VMware, it’s time to make sure everything performs properly.

Here Pandora FMS is the answer, as it also includes a plugin for Proxmox that connects through the API to monitor LXC containers, VMs, and nodes, generating an agent that forwards data to Pandora’s server.

Don’t panic—the plugin is a pre-packaged binary including all dependencies (you’re welcome), sparing you the usual Linux dependency maze.

As is common in Linux, you may customize the plugin with a configuration file (parameter details and sample file here and a step-by-step guide here).

When executed, the plugin creates agents and modules so you may easily monitor your Proxmox infrastructure from Pandora FMS.

Lessons Learned

• License and support savings, since Proxmox itself is free and offers optional support contracts.
• Greater control over resources, thanks to open code and transparency—plus the possibility to adapt it further if you have the time and skills.
• Straightforward monitoring with Pandora FMS, as seen above: install the plugin and start collecting critical data.

Now let’s take it one step further.

Scenario 3: Monitoring Hybrid Environments after Migrating from VMware

No Star Trek TNG “Best of Both Worlds” jokes here—but most IT infrastructures aim to benefit from several technologies. Sometimes hybrid setups are a choice; other times, a necessity.

For example, you might have a Windows Server running a couple of VMs with Hyper-V but no budget for additional licenses—so you use Proxmox for the rest.

Eventually, almost every IT landscape becomes a miniature UN: multiple systems, multiple “languages”, and components that rarely get along.

No problem—Pandora FMS works as the universal translator and centralized repository for monitoring and key insights.

That’s its biggest advantage and our core obsession: one ring to rule them all, the Rosetta Stone that translates every technology into a single language and shows all vital information together.

Thousands of systems, one intelligence—that’s our goal! But let’s see how it actually works!

Hybrid monitoring with Pandora FMS use case

Let’s make life tough for our IT manager. Imagine an organization migrating from VMware that already had everything well monitored but is unsure which way to go.

During the meeting, management says (as usual) that the budget is near zero but they still expect VMware-level performance.

The IT manager suggests virtualizing a couple of machines using Hyper-V, leveraging an existing Windows Server license and their prior experience with that console.

Given the needs—and invisible budget—they offer using Proxmox for the rest of the virtualization, as they have reviewed its features and found them suitable.

As always, some middle manager feels compelled to say something smart to justify their salary, so they mention Red Hat OpenShift (thanks ChatGPT).

The CEO then asks the IT manager to include that option in the pilot project.

Of course, they want a report comparing performance with VMware within two weeks, and everything must integrate into complete monitoring of all non-virtual infrastructure elements.

Our weary IT manager has no choice but to build a virtual Frankenstein. At least they have one advantage—they use Pandora FMS for monitoring.

After deploying Proxmox on a test server, using Windows Server for two VMs, and installing OpenShift to keep the boss happy, their virtualization landscape looks like this:

• 2 VMs running on Hyper-V.
• 4 VMs on Proxmox plus storage and network.
• 1 VM running OpenShift.
• The original VMware infrastructure still in production, used for baseline comparison.

Luckily, Pandora FMS has a plugin for OpenShift, allowing them to deploy all monitoring easily. Despite the heterogeneity, the key information for our manager is unified within the Pandora FMS console.

Everything appears as a single monitored entity, enabling several advantages:

• Unified control over heterogeneous components.
• Easy creation of comparative reports between alternatives and compared to VMware, showing performance improvement or loss and identifying the best migration option per criterion (e.g. resource consumption).
• Centralized alerts for every component, regardless of platform.

Those outcomes deliver results such as:

• Shorter monitoring deployment time.
• Reduced MTTR (mean time to repair) since everything is controlled from a single command center.
• Unified visibility in hybrid environments, including elements beyond virtualization—like that shiny CRM cloud app or the on-premise database server still running in the basement next to the steam boiler.

That way, they deliver their report on time—with critical insights on which post-VMware options will support the next stage and maintain key metrics like SLA compliance.

Comparison Between Scenarios

Let’s summarise the key aspects of the scenarios in the following table:

How Pandora FMS Eases the Post-VMware Transition

The key takeaway: regardless of the chosen path, a unified monitoring platform Pandora FMS is essential for success.

It works as a universal translator, quickly deploying across new environments and maintaining telemetry continuity—capable of monitoring even less common virtualization systems.

Recommendations for Planning Monitoring After Leaving VMware

• Pre-Migration Assessment: Compile a complete inventory of critical VMware metrics and ensure your new tool can replicate them.
• Phased Migration: Start with a pilot project and monitor simultaneously to avoid “data gaps” during the transition.
• Historical Data Retention: Configure Pandora FMS (or your chosen tool) to collect data from the new environment before decommissioning VMware, enabling pre- and post-migration performance comparison.
• Automation and Alerts: Use the migration as a chance to review and refine notification and alerting policies.

Conclusions and Next Steps

It’s undeniable that VMware leaves a hard-to-fill gap. Migration costs—whether in reduced performance, missing features, or lower metrics—can be higher than expected if you don’t monitor properly.

Our first recommendation, naturally, is Pandora FMS. But don’t take our word for it—see for yourself by testing it free of charge and commitment.

Experience first-hand how Pandora FMS adapts to VMware alternatives and why it becomes the simplest part of an otherwise complex migration.