When I restart/activate/upgrade the On-Premise Poller, why is it not showing data immediately
The following may be one of the following reasons for data not showing up after restarting/activating/upgrading the On-Premise Poller:
- In cases where there is a large number of monitors pointed to the On-Premise Poller, data collection for all these monitors will consume a considerable amount of time. This is because only 40 Kb of data is sent to the Site24x7 server every 5 minutes. Thus, data posting for a large number of monitors will take some time for the data to show up on the dashboard
- Another possible reason may be a communication failure between the Site24x7 server and the On-Premise Poller. In such cases, the data will be stored in the local server and when the Poller is restarted, a considerable amount of time will be consumed for sending all the stored data.
Refer here for troubleshooting steps if there is a communication failure between the Site24x7 server and the setup On-Premise Poller

The threshold for sending and receiving the On-Premise Poller data is 5 minutes. So, the user is requested to wait for a maximum of 5 minutes to view the data on the dashboard
Related Articles
Exclude the selective SSH algorithms in On-Premise Poller during SFTP Transfer monitoring
By excluding SSH algorithms, you can restrict Site24x7 SSH Client from using the excluded algorithm while connecting to the SSH server during SFTP Transfer monitoring. Follow the steps mentioned below for SSH algorithm exclusion in On-Premise Poller ...
Synthetic browser module prerequisite and troubleshooting guide for On-Premise Pollers
Introduction This document provides a structured troubleshooting guide for resolving issues encountered during the download process of On-Premise Poller for Synthetic (Browser) Module. It covers possible statuses, check-up steps, remedies, and ...
Monitors that require On-Premise Pollers in Site24x7
Certain monitor types in Site24x7 require the use of On-Premise Pollers for data collection, especially when monitoring internal, firewall-restricted, or private resources. Depending on the type of monitoring, additional modules like the Network ...
Resolving huge disk space issues with the On-Premise Poller and Network Module
Often huge disk space results from the heap dump files in the NetworkPlus/bin directory of the On-Premise Poller. What are HPROF files? HPROF files are used to store Java virtual machine (JVM) memory dumps. When a JVM runs out of memory (OOM), it ...
Understanding latency in data center operations
Latency, measured in milliseconds (ms), is the time taken for a response to be generated by an application or service. Lower latency results in quicker responses. Latency can occur due to several factors like: Network traffic: High volumes can slow ...