How To Edit A Resource Manager Report To Prevent UI Hangs Or Poor UI Performance

Applies To

  • Zenoss 4.2.3


Running a report with default settings can result in poor UI performance or even UI hangs in deployments where Zenoss has many items in the default device organizer (device class) for the report. Many Resource Manager reports automatically run when the report name is clicked. To populate the report, information from all devices in the report's default device organizer is accumulated and loaded. If the number of items in the default device organizer is very large, the time and resources required to render the information can cause delays and impact performance.

The following Enterprise Reports may load data for a large number of devices in larger Zenoss deployments:

  • 95th Percentile
  • Cisco Inventory
  • Data Sources in Use
  • Defined Thresholds
  • Interface Utilization
  • Organizer Availability
  • Organizer Graphs

Note: This list is not exhaustive and device counts for these reports will vary with each deployment.

To prevent this issue, the default report settings can be edited to load the devices from a different device organizer with fewer devices, reducing the load imposed on Resource Manager to generate the report.

Example Scenario

For this scenario, assume you want to generate the Interface Utilization report. This report includes all items in the
/Devices/Network device organizer. To generate the report, you perform the following steps:

  1. Click the Reports tab.
  2. From the left pane, navigate to Enterprise ReportsInterface Utilization.
  3. Wait for the report to display in the right pane.

In our example scenario, we assume the /Devices/Network class contains thousands of devices. This means the Interface Utilization report requires a long time to load and you cannot perform other functions until the report loads completely.

To rectify this problem, edit the report to load data from a different device organizer than the default /Devices/Network class (labeled the Root Organizer in this report), shown in the following figure.

Note: Depending on the Enterprise Report you chose, the field that identifies the initial device organizer path in the right panel might be labeled as Device Class, Root Organizer, or Organizer.

In our example scenario, assume the /Devices/KVM class has a small number of devices. You can edit the Interface Utilization report to load data from this device class by default instead of the default class of /Devices/Network/.

Use the following procedure to change the initial device organizer path.


Note: This procedure requires a login to the Zope Management Interface, and therefore requires the logged on user to have the Manager role. With slight variation, the procedure can be used for reports other than the report illustrated here.

  1. Enter the following URL into your browser. Substitute your Zenoss host name:
  2. Click Enterprise Reports from the left pane to expand the report options.
  3. Click InterfaceUtilization to load the page template in the right pane.
  4. In the page template, search for the the appropriate line in the report template.
    In this example, find "organizer python:sts(tableName, 'organizer', '/Devices/Network');
  5. Change the value specified for the organizer (in this case '/Devices/Network') to point to the more sparsely populated /Devices/KVM device organizer.

    In the example below, the path /Devices/Network has been changed to /Devices/KVM:


  6. Click the Save Changes button.
  7. Exit the Zope Management Interface by loading the URL for the Zenoss interface (http://YourZenHostName:8080)

After completing this procedure, the next time the initial Interface Utilization report runs, it loads the items in the /Devices/KVM. Because there are fewer items in that device organizer, the initial results return quickly.

Was this article helpful?
0 out of 0 found this helpful


Powered by Zendesk