Notes

The following section provides additional information or procedures regarding Analytics issues.

ANA-223: Wide performance ETL batches have ability to blow out the Heap in CentralQuery service.

If you define too large of a period for a performance ETL batch, for example 24 hours instead of just 4 hours, you may blow out the Heap and receive error messages similar to the following in zenoss_analytics.out:
2017-03-07 13:59:07,748 ERROR perfextractjob-8 com.zenoss.reporting.extract.service.PerfExtractionTask - Failed to execute request: Unexpected end of ZLIB input stream task="fs_inodes__pct-4052", batch=8746, exception=EOFException
2017-03-07 13:59:07,748 ERROR perfextractjob-6 com.zenoss.reporting.extract.service.PerfExtractionTask - Failed to execute request: Unexpected end of ZLIB input stream task="fs_inodes_used-4050", batch=8746, exception=EOFException
2017-03-07 13:59:07,748 WARN  quartzScheduler_Worker-6 com.zenoss.reporting.schedule.ExtractPerfJob - [ExecutionException] java.io.EOFException: Unexpected end of ZLIB input stream
2017-03-07 13:59:07,748 WARN  quartzScheduler_Worker-6 com.zenoss.reporting.schedule.ExtractPerfJob - [ExecutionException] java.io.EOFException: Unexpected end of ZLIB input stream
2017-03-07 13:59:07,748 ERROR perfextractjob-7 com.zenoss.reporting.extract.service.PerfExtractionTask - Failed to execute request: Bad Gateway   task="fs_used__pct-4051", batch=8746, exception=HttpResponseException
2017-03-07 13:59:07,749 ERROR perfextractjob-4 com.zenoss.reporting.extract.service.PerfExtractionTask - Failed to execute request: Bad Gateway   task="fs_used__pct-4048", batch=8746, exception=HttpResponseException
2017-03-07 13:59:07,748 ERROR perfextractjob-1 com.zenoss.reporting.extract.service.PerfExtractionTask - Failed to execute request: Bad Gateway   task="fs_used__pct-4045", batch=8746, exception=HttpResponseException
2017-03-07 13:59:07,750 ERROR quartzScheduler_Worker-6 com.zenoss.reporting.schedule.ExtractPerfJob - [HttpResponseException] Bad Gateway
2017-03-07 13:59:07,750 ERROR quartzScheduler_Worker-6 com.zenoss.reporting.schedule.ExtractPerfJob - [HttpResponseException] Bad Gateway

To remedy this situation, you need to adjust the QueryService RAM commitment from its current value to 4G, and retry the batch.

To increase the QueryService RAM commitment, perform the following:
  1. In Control Center, navigate to the CentralQuery service of your deployed Zenoss application Zenoss.resmgr > Zenoss > Metrics > CentralQuery.
  2. Click the Edit Service link near the top of the page.
  3. In the dialog box, locate the field labeled RAM Requested and change the value in that field to 4G. If the value is already 4G or has a larger value, then make no changes.
  4. Click Save Changes.

ZPS-757: RPN syntax error in several aliases

This issue has been resolved in the Linux Monitor ZenPack version 2.2.6. If your Resource Manager instance is running an earlier version of this ZenPack, you need to upgrade to version 2.2.6 or higher.