Howdy,

Thanks, James.

Since the job IDs and names are unique, I can't really do a single
script for each job.  I believe that restricts me from using the
command datasources, since I can only parse a single line of output in
each Nagios plugin.

Let the coding begin. :)

  -Mike

On Tue, Sep 16, 2008 at 8:12 AM, James Pulver
<[EMAIL PROTECTED]> wrote:
> I think you would need to use a script to pull each job individually if you
> wanted individual events for them. To clarify, I'm not aware (Chet might
> contradict me here) of how to generate multiple events from one script...
>
> Your guess at the end sounds right to me, though you might have the
> terminology wrong - I think you could do this with command datasources like
> the Nagios plugin, which I would think would be easier than a custom
> collector (a la ZenSNMP...).
> --
> James Pulver
> Information Technology Area Supervisor
> LEPP Computer Group
> Cornell University
>
>
>
> Mike DeGraw-Bertsch wrote:
>>
>> Howdy,
>>
>> Figured I'd ask once more since my original posting doesn't seem to
>> have made it to the mailing list.
>>
>>  Thanks!
>>  -Mike
>>
>> --
>>
>> Howdy,
>>
>> I'm setting Zenoss up to monitor my production environment, and things
>> have been going swimmingly in terms of the systems and processes I
>> need to monitor.
>>
>> Where I'm running into trouble, however, is monitoring the
>> applications that run on my servers. We use an MS SQL database to
>> track currently running jobs, and to identify jobs that have failed.
>> I'd like to have Zenoss query the SQL server to get a list of all of
>> the failed jobs, and create an individual event for each failed job.
>>
>> I created a check based on the check_mssql Nagios plugin (which runs
>> arbitrary SQL queries) to identify all of the failed jobs, which of
>> course only creates a single event. Any thoughts on how I could create
>> an individual event for each failed job?
>>
>> Right now, the check_mssql will return something along the lines of:
>>
>> CRITICAL: 3 failed jobs: Job_12345, Job_39383, Job_39293F
>>
>> And while it's great that I get an event with that line in it, I'd
>> much prefer to get separate events for each job, so that event
>> deduplication doesn't obscure when the failed jobs have changed. To
>> clarify, currently in the example I gave, if Job_12345 got resolved
>> and a new job failed, my check count goes up and the summary message
>> changes, but I don't believe that an additional notifications gets
>> sent out.
>>
>> I'm guessing I'm going to have to write a plugin with a custom collector?
>>
>> Thanks to anyone for thoughts and suggestions!
>> -Mike
>> _______________________________________________
>> zenoss-users mailing list
>> [email protected]
>> http://lists.zenoss.org/mailman/listinfo/zenoss-users
>
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users
>
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to