Hi Pijush;

The polling time is controlled by the "step" setting in the "*** Database ***" section of the configuration file.  However, it is important to note that any change to this setting means that you will have to either delete all of your existing RRD files (and lose all the history), or convert the existing data to the new step value (a fairly tedious process).

There are, however, other possible solutions, depending on your available system & network resources and monitoring requirements:

- Reduce the value of the "pings" variable to ping each host fewer times during each polling session.   Note that changing this option also requires regeneration of your RRD files.

- Enable the "concurrentprobes" option and define multiple instances of your probe, and then select groups of hosts to use each probe.  With the concurrentprobes option enabled, each group will be polled as a separate process and function independently.   Make sure you have enough disk I/O and network capacity to support this before running it in production!   Examples of how to set this up can be found as Example 3 in the smokeping_examples page (http://oss.oetiker.ch/smokeping/doc/smokeping_examples.en.html).


- Pete

Dear Sir,

I work in a Internet Service Provider in Bangladesh. I use Smokeping in our office to monitor our customers. Now-a-days I am facing a problem. I have more than 500 users in my smokeping Target. When the limit of unreachable hosts increased no graphs plotted in Smokeping. I come to know that the polling time takes more that default (300 s). How can I increase the polling time? Or any other solution? Please help.

Thanks,

Pijush Chowdhury.

_______________________________________________ smokeping-users mailing list smokeping-users <at> lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users