Nagios service latency

[sunchai (gillnaldo : sun)]

Hi all,

   I faced problem with nagios service latency. My requirement is active service monitoring to router/ network device using "SNMP" and "Ping" command. My environment is big router with ~100 services per device.

   How can I optimized nagios config? Thank in advance.

Note: I have information below
########## nagios -s ################
HOST SCHEDULING INFORMATION
---------------------------
Total hosts:                     173
Total scheduled hosts:           173
Host inter-check delay method:   NONE
Host inter-check delay:          0.00 sec
Max host check spread:           2 min
First scheduled check:           Tue Oct 30 18:55:33 2007
Last scheduled check:            Tue Oct 30 18:55:33 2007


SERVICE SCHEDULING INFORMATION
-------------------------------
Total services:                     1071
Total scheduled services:           1071
Service inter-check delay method:   NONE
Inter-check delay:                  0.00 sec
Interleave factor method:           SMART
Average services per host:          6.19
Service interleave factor:          7
Max service check spread:           3 min
First scheduled check:              Tue Oct 30 18:55:33 2007
Last scheduled check:               Tue Oct 30 18:55:33 2007


CHECK PROCESSING INFORMATION
----------------------------
Service check reaper interval:      10 sec
Max concurrent service checks:      2000

####### nagiostats ############
Total Services:                       1071
Services Checked:                     1071
Services Scheduled:                   1071
Active Service Checks:                1071
Passive Service Checks:               0
Total Service State Change:           0.000 / 28.360 / 0.321 %
Active Service Latency:               0.131 / 162.251 / 63.118 sec
Active Service Execution Time:        0.034 / 12.306 / 2.001 sec
Active Service State Change:          0.000 / 28.360 / 0.321 %
Active Services Last 1/5/15/60 min:   93 / 1071 / 1071 / 1071
Passive Service State Change:         0.000 / 0.000 / 0.000 %
Passive Services Last 1/5/15/60 min:  0 / 0 / 0 / 0
Services Ok/Warn/Unk/Crit:            1011 / 0 / 2 / 58
Services Flapping:                    2
Services In Downtime:                 0

Total Hosts:                          173
Hosts Checked:                        173
Hosts Scheduled:                      173
Active Host Checks:                   173
Passive Host Checks:                  0
Total Host State Change:              0.000 / 12.370 / 1.127 %
Active Host Latency:                  0.000 / 441.785 / 258.783 sec
Active Host Execution Time:           2.519 / 2.632 / 2.534 sec
Active Host State Change:             0.000 / 12.370 / 1.127 %
Active Hosts Last 1/5/15/60 min:      17 / 67 / 173 / 173
Passive Host State Change:            0.000 / 0.000 / 0.000 %
Passive Hosts Last 1/5/15/60 min:     0 / 0 / 0 / 0
Hosts Up/Down/Unreach:                172 / 1 / 0
Hosts Flapping:                       0
Hosts In Downtime:                    0

####### My hardware ########
CPU: Xeon 2.8 x 2
RAM: 4 GB
Disk: SCSI 36 GB 10000 RPM

BR,
Gillnaldo SC -

 __________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20071030/10821a30/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null