Slow web console when monitoring SolarWinds Virtual Infrastructure Monitor (VIM) using Azure Databricks

When configuring SolarWinds Virtual Infrastructure Monitor (VIM) to monitor virtual machines using Azure Databricks, users may experience severe performance degradation across various features. Common symptoms include slowness when adding nodes, delayed page loads, and prolonged network discovery processes.  Additional symptoms observed in logs include (but not limited to):

• Long delays when adding nodes
• Intermittent poller errors and exceptions (TransientApiProxyException)
• Slowness across SolarWinds UI, including Network Discovery
• Log errors involving SWIS timeouts, macro parsing failures, and database deadlocks

This issue occurs because Azure Databricks creates and removes VMs multiple times daily, each with new unique IDs. SolarWinds treats these as distinct devices, leading to a buildup of orphaned polling data that cannot be inserted into the database, degrading performance.

As of May 2025, Azure Databricks is not officially supported with SolarWinds Platform.  To workaround the problem:

1. Temporarily disable automonitoring for Azure Databricks VMs to prevent the buildup of orphaned polling data.
2. Manually manage VM discovery and polling until SolarWinds adds support for Azure Databricks.

The following knowledge base articles below cover common problems. We recommend reviewing them as they may help resolve other related performance issue quickly.

• SWIS connection timeouts and slowness caused by CRL
• Turn off Windows automatic root certificates updates in the SolarWinds Platform

It is important to note there may be multiple reasons for slow web console performance.  SolarWinds is constantly working on updating articles with the most relevant information.  Please continue to monitor these articles for updates in the future.