|
|
|
|
|
|
|
|
|
|
|
|
|
|
Using probes to monitor your Domino servers (continued)
When each probe is set up, you then need to configure the event notification for when each probe is not able to access its destination resource. In other words, the way it will tell you there's something wrong. Event configuration is largely unchanged from R4. You have the option to send your notifications via Notes broadcast or to log it to a database, an email, a log entry in NT Application Log, or a pager. You can also configure it to run a program, to relay to another server or an SMTP trap, or to log to the UNIX system log. The simplest way to configure event notification for each probe is to click "Create a new notification profile for this event" on each of the probes as they are created. This launches the Event Notification Setup Wizard that simplifies the creation of the event notification document.
Probe statistics
The generated statistics (measured in milliseconds) won't be able to be used to measure the end-to-end response time a user will actually experience, but if you keep track of the relative statistics, they can be used for capacity planning and monitoring of server loads. A value of -1 means that the probe is not able to receive a response within the timeout threshold for that monitored resource.
Table A shows the statistics that are available once the appropriate probes have been created and are in operation.
| Type of Probe |
Statistic |
| Domino server |
Server.probingserver.destinationserver |
| Mail self-probe |
QOS.Mail.Ispy on server.ResponseTime |
| Mail probe on another server (to a specific recipient) |
QOS.Mail.recipicent.ResponseTime |
| TCP probe of DNS port |
QOS.DNS.server.event.ResponseTime |
| TCP probe of FTP port |
QOS.FTP.server.event.ResponseTime |
| TCP probe of HTTP port |
QOS.HTTP.server.event.ResponseTime |
| TCP probe of IMAP port |
QOS.IMAP.server.event.ResponseTime |
| TCP probe of LDAP port |
QOS.LDAP.server.event.ResponseTime |
| TCP probe of NNTP port |
QOS.NNTP.server.event.ResponseTime |
| TCP probe of POP3 port |
QOS.POP3.server.event.ResponseTime |
| TCP probe of SMTP port |
QOS.SMTP.server.event.ResponseTime |
Below is the output from the SHOW STAT server console command that relates to probe response times.
QOS.DNS.CN=servera/O=Sydney.GNEN-4BGQ3J.ResponseTime = -1
QOS.FTP.CN=servera/O=Sydney.GNEN-4BGQ3J.ResponseTime = -1
QOS.HTTP.CN=serverb/O=Sydney.SHOE-4A95T4.ResponseTime = 60
QOS.HTTP.CN=servera/O=Sydney.GNEN-4BGQ3J.ResponseTime = 351
QOS.IMAP.CN=serverb/O=Sydney.SHOE-4A95T4.ResponseTime = 70
QOS.IMAP.CN=servera/O=Sydney.GNEN-4BGQ3J.ResponseTime = 120
QOS.LDAP.CN=serverb/O=Sydney.SHOE-4A95T4.ResponseTime = 60
QOS.LDAP.CN=servera/O=Sydney.GNEN-4BGQ3J.ResponseTime = 90
QOS.Mail.CN=Greg Neilson/O=Sydney.ResponseTime = 5
QOS.Mail.ISpy on serverb.ResponseTime = 0
QOS.NNTP.CN=serverb/O=Sydney.SHOE-4A95T4.ResponseTime = 70
QOS.NNTP.CN=servera/O=Sydney.GNEN-4BGQ3J.ResponseTime = -1
QOS.POP3.CN=serverb/O=Sydney.SHOE-4A95T4.ResponseTime = 20
QOS.POP3.CN=servera/O=Sydney.GNEN-4BGQ3J.ResponseTime = 20
QOS.SMTP.CN=serverb/O=Sydney.SHOE-4A95T4.ResponseTime = 30
QOS.SMTP.CN=servera/O=Sydney.GNEN-4BGQ3J.ResponseTime = -1
Server.CN=serverb/O=Sydney.CN=serverb/O=Sydney = 10
Server.CN=serverb/O=Sydney.CN=servera/O=Sydney = 10
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-- Advertisement --
Sophisticated Meets Simple For Document Management
Share. Control. Manage.
Documents, emails, and content in the context of how work is done.
Native to Lotus Domino. The User Experience unseen for Lotus Domino.
Do more with less. Really.
See the possibilities Docova unleashes for Lotus Domino. |
-- Advertisement --
Teamstudio Edition 25 has shipped
It's finally here! Now that Teamstudio Edition 25 has shipped, listen to our latest Tool Time audio program to find out what's changed. Updates to all your favorite Teamstudio tools will be discussed.
Plus, you'll get an introduction to Teamstudio Undo (formerly known as Teamstudio Snapper).
Tap here to get started! |
|
|
|
|
|
|
|
|
|
|
