[Nagiosplug-help] check_interval threshold

[Khan, Tony (A&E)]

Thank you so much for your help Marc.

My Service definition setting looks like this, should I just add '
interval_length 1' under check_period? Please advise.  


##### Generic service definition template #####
define service{
        name                            generic-service
        active_checks_enabled   1       ; Active service checks are
enabled
        passive_checks_enabled  0       ; Passive service checks are
enabled/disabled
        parallelize_check               1       ; Active service checks
should be parallelized
                                              ; (disabling this can lead
to major performance problems)
        obsess_over_service     1       ; We should obsess over this
service (if necessary)
        check_freshness         0       ; Default is to NOT check
service 'freshness'
        notifications_enabled   1       ; Service notifications are
enabled
        event_handler_enabled   0       ; Service event handler is
disabled
        flap_detection_enabled  0       ; Flap detection is disabled
        process_perf_data               1       ; Process performance
data
        retain_status_information       1       ; Retain status
information across program restarts
        retain_nonstatus_information    1       ; Retain non-status
information across program restarts
    check_period                        24x7
        max_check_attempts      3
        normal_check_interval   1
        retry_check_interval    1
        notification_interval   120
        notification_period     24x7
        notification_options    w,u,c,r
        register                        0
        }

-----Original Message-----
From: Marc Powell [mailto:marc at ena.com] 
Sent: Thursday, January 07, 2010 10:47 AM
To: Nagios Plugin Help List
Subject: Re: [Nagiosplug-help] check_interval threshold


On Jan 6, 2010, at 8:03 PM, Khan, Tony (A&E) wrote:

> 
> Hi all,
> 
> 
>         Can Nagios monitors (plugins) run within 1 and 10 second
interval?  We have to do a performance based testing of Nagios and we
want to do it for 1 second sampling for CPU, memory, network I/O etc.
Can someone please advise if this is possible?  If not, what's the
lowest check_interval threshold I can set? 


In theory, yes; in reality, there are too many variables to guarantee
it.

You can set interval_length to '1' to have every _interval variable
measured in seconds. a check_interval of 1 would be 1 second. a
check_interval of '10' would be 10 seconds. If your OS can
instantiate/launch the plugin, your plugin perform whatever action it's
doing, return the results to nagios, nagios process the results, all in
under 1 second, and be ready to launch another instance at the next
second *and* nagios isn't busy processing a bunch of these at the same
time or doing other things, you may be able to have a 1 second
check_interval. My guess is that those things are going to take more
than one second to accomplish though.

You should really just Try And Find Out if it works in your
configuration. Note that when you change interval_length, you'll need to
adjust every *_interval value to compensate for your change since it's
the basis for those.

--
Marc


------------------------------------------------------------------------
------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and
easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Nagiosplug-help mailing list
Nagiosplug-help at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
::: Please include plugins version (-v) and OS when reporting any issue.

::: Messages without supporting info will risk being sent to /dev/null

--------------------------------------------------------------------------
This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. The information contained in this e-mail was obtained from sources believed to be reliable; however, the accuracy or completeness of this information is not guaranteed. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Past performance is no guarantee of future results. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
--------------------------------------------------------------------------