Network Management

Turn on and use Hubble with Orion modules

This article describes how to use the Hubble Active tool.

First published date

10/23/2018 9:08 AM

Last published date

3/1/2022 9:37 PM

Overview

Hubble is a tool for analyzing web server response time. SolarWinds Support may ask you to use Hubble to identify the source of a performance problem.

You can use Hubble to determine why you are experiencing slow website performance and to identify the source of the problem.

Product section

Network Performance Monitor

Resolution

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.

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:

  • Database time
  • Business layer time
  • Other time

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:

When you are finished

Be sure to turn off Hubble when you are finished using it to avoid excess consumption of resources.