How can I check and troubleshoot issues with the Reporting Services' on-prem instance?  This article provides instructions on how to check whether the on-prem instance of Reporting Service is running, how to start and stop the Reporting Service, where to find the logs for on-prem installations, and troubleshoot login and report readability issues. By following these guidelines, you can effectively manage and resolve any issues related to the Reporting Service. These steps are applicable to On-prem Controllers and Support will check these for SaaS customers. In this article... How do I determine whether the Reporting Service is running? How do I start and stop the Reporting Service? Where can I find Reporting Services logs?  How do I troubleshoot login issues and unreadable reports? How do I enable debug mode to generate debug logs for troubleshooting reports? How do I check the on-prem instance of the Reporting Service (RS)? To determine if the on-prem instance of Reporting Service is running, follow these steps: Open the command line interface on your system. Enter the command ps aux | grep node . Look for the process node reporting_service/reports/index.js . If you find this process, it indicates that the Reporting Service is running. BACK to top How do I start and stop the Reporting Service (RS)? To start or stop the Reporting Service, use the following instructions: Navigate to the reporting_service/reports/bin directory. Use the command cd reporting_service/reports/bin to change the directory. To stop the Reporting Service, execute the command ./reports-service.sh stop . To start the Reporting Service, execute the command ./reports-service.sh start . BACK to top Where do I locate the Reporting Service (RS) logs? On-Prem: The logs can be found at <CONTROLLER_INSTALLATION_FOLDER>/reporting_service/reports/logs. BACK to top How do I troubleshoot login issues and unreadable reports? If the Reporting Service is unable to log in or the reports display a login screen, it may be due to one of the following reasons: Broken credentials in the Reporting Service. Connectivity issues preventing the Reporting Service from logging in. The controller has been configured with an incorrect deep link. Verify the "-Dappdynamics.controller.ui.deeplink.url" VM argument. How do I enable debug mode in the Reporting Service to generate debug logs for troubleshooting reports? To enable debug mode in the Reporting Service, follow these steps: Stop the reporting server: Navigate to the <controller_home>/reporting_service/reports/bin directory. Execute the command ./reports-service.sh stop . Enable debug log for reporting: Open the <controller_home>/reporting_service/reports/config/default-config.json file. Locate the "level" value and change it to "debug". Change the value for the key "phantomDebugFlag" to "true". Start the reporting server: Navigate to the <controller_home>/reporting_service/reports/bin directory. Execute the command ./reports-service.sh start . Analyze the logs to see any errors and exceptions. NOTE | Remember to revert the above settings after collecting the debug logs. If you require further assistance or have any questions, please reach out to our Support team. BACK to top ... View more

Zero fill is a form of over-the-wire compression. Agents do not send metrics to the Controller if the metrics value is 0. This keeps packet sizes smaller. The Controller keeps a record of metrics that were reported previously and when they were reported previously. Using this information, the Controller fills in metrics that weren't sent and have had data sent in the last 60 mins.  Zero-filling only happens when an agent is running and uploads metrics. If an agent goes down, there will be no zero-filling for the period the agent is down.  minor revision made to product capitalization. C Landivar    ... View more