Overrides

Everyone knows that Red = Bad. Two people working to fix the same thing is also bad. An override is a way of saying "I know it is down" or "I'm working on it".

Overrides are typically used in the 2 following ways:

Setting an Override

  1. Click on the "Override" button on the webpage.
  2. Fill in the fields.
  3. Click "Submit"
  4. Depending on company policy, create a trouble-ticket.
  5. Fix problem.

In order to set an override on an object that is currently "up", manual mode must be used. Otherwise, immediately after being set, it will notice the object is up, and automatically disengage.

Preventing Overriding

Often, there are things that should be able to be overridden (such as a router), and things that should not be (such as "our entire east coast network"). This can be specified in the config file:

	Group "East Coast Network" {
		overridable:	no
		Host "gw-phila1" {
			Service Ping
		}
		Host "gw-nyc1" {
			Service Ping
		}
		...
	}

Additionally, you can control who can and cannot override what on a per user, per object basis using access control lists. Overrides are protected by "acl_override" (or, in simple mode, "acl_staff").