[Nagios-devel] 3.0 FEATURE REQUEST: Visibility directive
Posted: Thu Mar 08, 2007 10:49 am
This is a MIME message. If you are reading this text, you may want to
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.
--=__Part311589B6.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
In reading the "Nagios Web Interface Wishlist" article on nagioscommunity.org I
was reminded of an issue that I have run into where a person will want to be
notified for services x, y, and z but not services a, b, or c. However, they
want to see a, b, c, x, y, and z in the CGI front-end. This would be possible if
we disable notifications for service a, b, and c--except that other people want
those notifications.
If some sort of "visibility" directive were added to hosts and services. You
could specify contacts which can see the host/service in the CGI/PHP front-end,
but receive no notifications. This directive should be additive to the contacts
(contactgroups) directive in that anyone who is being notified for a
host/service automatically has visibility.
I also will add to the article my thoughts that the host/service visibility
logic should be reversed. A contact with visibility to the host should not see
ALL services, but a contact with visibility to a service should be able to see
the host on which it resides. (example: A DBA doesn't necessarily care about the
webserver service, but will always care about the oracle service or if the host
is down.)
Thoughts?
Marlo
----------------------------------------------------------------------
NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
--=__Part311589B6.0__=
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Description: HTML
In reading the "Nagios Web Interface Wishlist" article on nagioscommunity.org I was reminded of an issue that I have run into where a person will want to be notified for services x, y, and z but not services a, b, or c. However, they want to see a, b, c, x, y, and z in the CGI front-end. This would be possible if we disable notifications for service a, b, and c--except that other people want those notifications.
If some sort of "visibility" directive were added to hosts and services. You could specify contacts which can see the host/service in the CGI/PHP front-end, but receive no notifications. This directive should be additive to the contacts (contactgroups) directive in that anyone who is being notified for a host/service automatically has visibility.
I also will add to the article my thoughts that the host/service visibility logic should be reversed. A contact with visibility to the host should not see ALL services, but a contact with visibility to a service should be able to see the host on which it resides. (example: A DBA doesn't necessarily care about the webserver service, but will always care about the oracle service or if the host is down.)
Thoughts?
Marlo
NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
--=__Part311589B6.0__=--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.
--=__Part311589B6.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
In reading the "Nagios Web Interface Wishlist" article on nagioscommunity.org I
was reminded of an issue that I have run into where a person will want to be
notified for services x, y, and z but not services a, b, or c. However, they
want to see a, b, c, x, y, and z in the CGI front-end. This would be possible if
we disable notifications for service a, b, and c--except that other people want
those notifications.
If some sort of "visibility" directive were added to hosts and services. You
could specify contacts which can see the host/service in the CGI/PHP front-end,
but receive no notifications. This directive should be additive to the contacts
(contactgroups) directive in that anyone who is being notified for a
host/service automatically has visibility.
I also will add to the article my thoughts that the host/service visibility
logic should be reversed. A contact with visibility to the host should not see
ALL services, but a contact with visibility to a service should be able to see
the host on which it resides. (example: A DBA doesn't necessarily care about the
webserver service, but will always care about the oracle service or if the host
is down.)
Thoughts?
Marlo
----------------------------------------------------------------------
NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
--=__Part311589B6.0__=
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Description: HTML
In reading the "Nagios Web Interface Wishlist" article on nagioscommunity.org I was reminded of an issue that I have run into where a person will want to be notified for services x, y, and z but not services a, b, or c. However, they want to see a, b, c, x, y, and z in the CGI front-end. This would be possible if we disable notifications for service a, b, and c--except that other people want those notifications.
If some sort of "visibility" directive were added to hosts and services. You could specify contacts which can see the host/service in the CGI/PHP front-end, but receive no notifications. This directive should be additive to the contacts (contactgroups) directive in that anyone who is being notified for a host/service automatically has visibility.
I also will add to the article my thoughts that the host/service visibility logic should be reversed. A contact with visibility to the host should not see ALL services, but a contact with visibility to a service should be able to see the host on which it resides. (example: A DBA doesn't necessarily care about the webserver service, but will always care about the oracle service or if the host is down.)
Thoughts?
Marlo
NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
--=__Part311589B6.0__=--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]