HP Labs Notification Mechanism Question

[Yogeeraj_1]

Hi,

here are mine:
1. message in syslog
2. e-mail to a user-supplied e-mail address
3. SMS administrator
4. blinking lights
5. e-mail to root at localhost
6. wall message / message to console
7. message in syslog
8. Openview/ITO event
9. SNMP trap
10.error during startup script execution
11.message in a product-specific logfile

Best Regards
Yogeeraj

[Tom Geudens]

Hi Brad,
Here's my list. I added EMS. Methods 1. to 4. are interchangeable in our environment since all these messages are "intercepted" by ITO/Openview.

01. Openview/ITO event
02. SNMP trap
03. EMS (!!!)
04. message in syslog
05. e-mail to root at localhost
06. e-mail to a user-supplied e-mail address
07. wall message / message to console
08. message in a product-specific logfile
09. blinking lights
10. error during startup script execution

Regards,
Tom

[George Petrides_1]

1-10 where 10 is the most used:

Notification mechanisms:
-----------------------------
8. e-mail to root at localhost
7. wall message / message to console
9. message in syslog
2. e-mail to a user-supplied e-mail address
10. Openview/ITO event
6. SNMP trap
5. blinking lights
3. error during startup script execution
4. message in a product-specific logfile

However, I had a dozen customers in the past with 1-2 systems, where in that situation the wall/console message and email to a user supplied e-mail address was the most useful notification way.

[avsrini]

Hi Brad,
Now-a-days sys admins manages more than one system and one system is managed by more than one sysadmin (shifts). And the servers are also
managed remotely. So checking each servers log file, mailing to one id, console messages, blinking lights are not adequate now. But everybody checks their emails very ofently while in the office and gets paged or SMS'd by customised scripts or programs on offtime. So a ideal noitification systems should be efficient enough to send the status to required persons quickly. We have aliased root mail id of all the servers
to sysadmins id's we get all the mails in single mailbox.

Here are my ratings.

1. email to a user-specified mail id
2. email to root at localhost
3. Openview / ITO event ( For paging )
4. message in syslog.
5. SNMP Trap
6. message in a product-specified logfile
7. wall message / messages to console
8. error during startup scripts
9. blinking lights.

[Suhas_2]

Hi,
My 2 cents.

We are using it as below
_____________________________________________
Mechanism Frequency
1>Openview / ITO event ALL CRITICAL 2>EVENTS.
3>SNMP Trap EVENTS on UAT/RND
4>message in syslog Preffered for Understanding the cause
5>e-mail Reporting about system statistics, reports but ALARMS ?.. never.
6>message in a product-specific logfile This thing proves to be very useful, only if the application is writing "good" logs, for example the logs written by Connect:Direct (NDM) from Serling commerce are extremely informative and most of the times those logs
help to find and fix the problem.
7> Wall message and mail to root may not give the kind of results, in few cases, like when I have a web-server on ISP segment and most services are internet based.

Suhas
^D

[Andreas D. Skjervold]

1. Openview/ITO event
2. e-mail to root at localhost
3. e-mail to a user-supplied e-mail address
4. SNMP trap
5. message in syslog
6. message in a product-specific logfile
7. wall message / message to console
8. error during startup script execution
9. blinking lights

rgds
Andreas

[Rainer von Bongartz]

1) e-mail to a user-supplied e-mail address

2) message in syslog

3) message to console

4) SNMP trap

5) message in a product-specific logfile

6)e-mail to root at localhost

7)error during startup script execution

8) Openview/ITO event e-mail to root at localhost

9) blinking lights