projected/recommended service check option

[Neil]

Hi Jeff, 

I also took out lines that are just paths. Here it is. 

check_external_commands=1
command_check_interval=5s
log_rotation_method=d
use_syslog=0
log_notifications=1
log_service_retries=0
log_host_retries=0
log_event_handlers=1
log_initial_states=0
log_external_commands=1
log_passive_service_checks=1
inter_check_delay_method=s
service_interleave_factor=s
max_concurrent_checks=15
service_reaper_frequency=10
sleep_time=1
service_check_timeout=60
host_check_timeout=30
event_handler_timeout=30
notification_timeout=30
ocsp_timeout=5
perfdata_timeout=5
retain_state_information=1
retention_update_interval=60
use_retained_program_state=0
interval_length=60
use_agressive_host_checking=0
execute_service_checks=1
accept_passive_service_checks=1
enable_notifications=1
enable_event_handlers=1
process_performance_data=0
obsess_over_services=0
check_for_orphaned_services=0
check_service_freshness=1
freshness_check_interval=60
aggregate_status_updates=1
status_update_interval=15
enable_flap_detection=0
low_service_flap_threshold=5.0
high_service_flap_threshold=20.0
low_host_flap_threshold=5.0
high_host_flap_threshold=20.0
date_format=us
illegal_object_name_chars=`~!$%^&*|'"<>?,()=
illegal_macro_output_chars=`~$&|'"<> 


Actually, below is how it looks now. I found out after tweaking 
service_reaper_frequency and interval_lenght. I even got it to a recommended 
value of 186. :) But I don't know if it's good for a production monitoring 
server. So I brought it down just to 15. 

       SERVICE SCHEDULING INFORMATION
       -------------------------------
       Total services:             76
       Total hosts:                43 

       Command check interval:     5 sec
       Check reaper interval:      10 sec 

       Inter-check delay method:   SMART
       Average check interval:     163.421 sec
       Inter-check delay:          2.150 sec 

       Interleave factor method:   SMART
       Average services per host:  1.767
       Service interleave factor:  2 

       Initial service check scheduling info:
       --------------------------------------
       First scheduled check:      1075414482 -> Thu Jan 29 14:14:42 2004
       Last scheduled check:       1075414643 -> Thu Jan 29 14:17:23 2004 

       Rough guidelines for max_concurrent_checks value:
       -------------------------------------------------
       Absolute minimum value:     5
       Recommend value:            15 

Let me know your recommendations. 

jeff vier writes: 

> On Wed, 2004-01-28 at 16:00, Neil wrote:
>> I tried nagios -s nagios.cfg and it gives me this. 
> <snip>
>> I don't know why I am just still having a 12 in recommended value. I already 
>> installed it on a 1 gig memory. And I am just monitoring 74 services for 
>> now.  What are the things that I need to tweak so I can have a good 
>> max_concurrent_checks value? 
>> If someone again can send there .cfg files, it will be awesome. This will 
>> give me an idea what things I am doing wrong. 
> 
> Run 'grep -v "^#" nagios.cfg |grep -v "^$"' and send that over and I
> (and maybe others) will have a look at it for you. 
> 
> (that just strips out the comments and blank lines - makes it plenty
> short for mailing list posting.) 
> 
 


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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