Troubleshooting report generation

Analytics server

The analytics-server installation logs are in the following location on an analytics server:

/opt/nsp/analytics/log

By default, an analytics server logs only errors. The server application log is the following:

/opt/nsp/analytics/log/analytics.server.log

You can enable additional logging using a script. See “To enable and manage analytics server logging” in the NSP System Administrator Guide for information.

The SQL log shows the data table names. Verify that the table for your report is requesting and receiving timed frame data to generate reports.

Additional logs are available in the following location on an analytics server:

/opt/nsp/os/tomcat/logs

For example, the analytics-registration.log file records analytics server communication with the NSP ZooKeeper service, and the tomcat catalina.out file records web-server operations and events.

Other reporting problems

The following may assist with troubleshooting Analytics reporting:

• See “Using Analytics” in the NSP Analytics Report Catalog to ensure that the reporting criteria are correctly specified. For example, all data for a report must be collected using the same collection interval.

• Verify the connectivity between the analytics servers, auxiliary database, and NFM-P main servers.

• If a report is taking a long time to execute, or generating errors, try reducing the number of objects in the data set.

• Verify that TLS is configured correctly in the NFM-P, and on each analytics server; see “TLS configuration and management” in the NSP Installation and Upgrade Guide for information.