[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.
Question
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
6.4

Syslog-NG notifications

Asked by timbrigham in Linux Network Security, Network Analysis Software, Message Queue

Tags: nagios

For some reason, I can't get my Nagios notifications up and working.
I'm trying to set up a new user to use a Perl script, which currently sits at /runme.pl

I think that I have all the various notification pieces in place - I've spent the last 3 hours going over the notification documentation on the nagios homepage - but I'm still missing something.
All necessary definitions should be included in the code section. 
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:

define host{
        name                    generic-switch-loud
        use                     generic-host
        check_period            24x7
        check_interval          5
        retry_interval          1
        max_check_attempts      10
        check_command           check-host-alive
        notification_period     24x7
        notification_interval   30
        notification_options    d,u,r,f,s
        contact_groups          admins
        register                0
        }
 
define service{
        name                            generic-service-loud
        active_checks_enabled           1
        passive_checks_enabled          1
        parallelize_check               1
        obsess_over_service             1
        check_freshness                 0
        notifications_enabled           1
        event_handler_enabled           1
        flap_detection_enabled          1
        failure_prediction_enabled      1
        process_perf_data               1
        retain_status_information       1
        retain_nonstatus_information    1
        is_volatile                     0
        check_period                    24x7
        max_check_attempts              3
        normal_check_interval           10
        retry_check_interval            2
        contact_groups                  admins
        notification_options            w,u,c,r,f,s
        notification_interval           60
        notification_period             24x7
        register                        0
        }
 
 
define host{
        use             generic-switch-loud
        host_name       cfcapc1
        alias           CFCA Switch 1
        address         cfcapc1
        hostgroups      switches
        contacts        syslog
        }
# Just to create a failing alert
define service{
        use                     generic-service-loud
        name                    ping_test
        host_name               cfcapc1
        service_description     PING TEST
        check_command           check_ping_other!10.100.100.1!200.0,20%!600.0,60%
        normal_check_interval   5
        retry_check_interval    1
        }
 
define command{
        command_name    notify-by-syslog
        command_line    /runme.pl "From Syslog"
        }
 
define contact{
        alias                           Syslog Generator
        contact_name                    syslog
        name                            syslog
        service_notification_period     24x7
        host_notification_period        24x7
        service_notification_options    w,u,c,r,f,s
        host_notification_options       d,u,r,f,s
        service_notification_commands   notify-by-syslog
        host_notification_commands      notify-by-syslog
}
 
define contactgroup{
        contactgroup_name       admins
        alias                   Nagios Administrators
        members                 nagiosadmin,syslog
        }
[+][-]04/15/09 06:05 AM, ID: 24147473Accepted Solution

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

About this solution

Zones: Linux Network Security, Network Analysis Software, Message Queue
Tags: nagios
Sign Up Now!
Solution Provided By: timbrigham
Participating Experts: 0
Solution Grade: A
 
 
Loading Advertisement...
20091021-EE-VQP-81 - Hierarchy / EE_QW_3_20080625