XML Schema for the categories.xml configuration file. This
file contains categories for the UI and reports. Version:
$Id$.
Top-level element for the categories.xml configuration
file.
Header for this file.
The category groups.
Header containing information about this configuration
file.
Revision of this file.
Creation time in the 'dow mon dd hh:mm:ss zzz yyyy'
format.
Monitoring station? This is seemingly
unused.
A category group containing categories. The only parts of
the category group that seem to be used are the common element and the
list of categories.
The name of the category group. This is seemingly
unused.
A comment describing the category group. This is
seemingly unused.
Common attributes that apply to all categories in
the group.
The categories belonging to this category
group.
Common attributes that apply to all categories in a
group.
A common rule that will be applied to all
categories in this group in addition to the category's
rule.
Categories belonging to a category group.
A category.
A category.
The category label. NOTE: category labels will need
to be unique across category groups.
A comment describing the category.
The normal threshold value for the category in
percent. The UI displays the category in green if the overall
availability for the category is equal to or greater than this
value.
The warning threshold value for the category in
percent. The UI displays the category in yellow if the overall
availability for the category is equal to or greater than this
value but less than the normal threashold. If availability is less
than this value, category is displayed in red.
A service relevant to this category. For a
nodeid/ip/service tuple to be added to a category, it will need to
pass the rule(categorygroup rule & category rule) and the
service will need to be in the category service list. If there are
no services defined, all tuples that pass the rule are added to
the category.
The category rule.