Skip to main content

This site will be migrated to HPE Support Center by 1 November 2023. The new URLs for the HPE GreenLake User Guide and HPE GreenLake Partner User Guide will be posted here by 3 October. More information coming soon!

Documentation - HPE Usage and Analytics

Reducing the scope of a report

There are two situations where as a report author or viewer you will not be able to see the full contents of a report. This article describes those situations and gives you suggestions for reducing the scope of a report to allow it to fully display.

The 10,000-row limit

To protect your browser from being overloaded, HPE GreenLake Central limits a report to displaying up to 10,000 rows of data. If the full result set of the report is more than 10,000 rows, this means that viewers cannot see some of these rows. There is no way to control or predict which rows are returned to the browser. Viewers will see only a subset of the data that they are expecting, but they might not realize it.

For this reason, if the report is truncated, the following error message appears:


Query errors

Sometimes a report fails to return any results. This could be due to a temporary issue with the reporting system, but more often is due to the result set for the report exceeding the capacity of the system. That is, the report simply requested too much data. In this case the reporting system protects itself by blocking the report query, and no results are returned to the browser.

Techniques for reducing your result set

Try one of the following techniques to reduce row count to below 10,000 or to reduce the amount of data returned by the report query.

See Creating and editing reports for step-by step instructions for using these techniques.

Filter your most unique column

The column with the most unique values is the biggest contributor to your row count. Add a filter to the report (or if the report is displayed as a widget on a page, add a filter to the page) that will reduce the number of unique values for this column.

Resource Name, Resource ID, and Accounting Date usually have many values, so if you don't know which column is your most unique and your report contains one or more of these, try them first.

Remove unnecessary columns

Each additional column adds rows to the report by creating new combinations of unique values, so remove columns you don't absolutely need. Some columns provide context that is nice to have, but not critical to the report's purpose. These are the columns to remove.

This option is only available if you have the right to edit the report in question.

Shorten the period

Each day means more usage records collected, which means more rows and more data returned by your report. Shorten the period for the report (or if the report is displayed as a widget on a page, the period for the page) to include only the dates you really need. You can use a custom period if you don't need a full week, month, or other common period.