Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Turn on and use Hubble

Turn on and use Hubble


This article describes how to use the Hubble Active tool. Hubble is a tool for analyzing web server response time, it helps you identify where your performance problem is.



  • All versions of Orion products



Turn on Hubble

  1. On the Orion Server, start the Log Adjuster.
    To do so, go to C:\Program Files (x86)\SolarWinds\Orion\LogAdjuster.exe (by default)
  2. In the LogAdjuster window, select True for Hubble Active, and click Apply.image.png

    To turn off Hubble again, Hubble Active to FALSE, and click Apply.

  3. Recreate the issue on the Web Console. You can see a red bar on the top left of your Orion Web Console.
  4. Click Details, and review the database, business layer, and other time.




Troubleshoot issues identified by Hubble

When enabled, the Hubble Summary shows the total time to load and percentage of total load time for three different categories:

View cached Hubble results

On the right of the Hubble Summary table, click the link to view recent Hubble results. 

Database Time

The time to query SQL from the Web Console (including SWQL).

  • Primarily from Web resources but it may contain some other information as well.
  • Long times here may indicate slow SQL performance or a misconfigured resource.

To troubleshoot database time issues, sort the list of queries below the summary by time and find out which SQL statement(s) are taking a long time.
For example, Alerting SQL Query for AlertStatus query where we are getting the most recent 250 triggered alerts. Rebuilding indexes will likely resolve this issue.

Business Layer Time

The time to get data from the Module Engine.

  • Module-specific operations and license details.
  • Long load times here may indicate bad table data or Module Engine communication issues.

To troubleshoot, check the log for running Business Layer queries in the query list and cross-reference the associated BusinessLayer Module log (ie: Core.BusinessLayer.log).

Other Time

The remaining load time after Database and BusinessLayer are complete.

  • SWIS connectivity, loading of IIS, .Net caches, and .Net object creation time.
  • High response times here may indicate old cache data or slow SWIS response time.
  • Errors in SWIS logs or communication issues with other polling engines may also cause this issue.

To troubleshoot other time issues:

  • Check the Orion.InformationService.log for long running queries 
  • Stop IIS, and clear the .Net cache in C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\*.




Last modified