Technical data

40 Monitoring and Alerting Policy Suite Administrator’s Guide
53-1002933-02
MAPS dashboard overview
6
• Fabric State Changes: Refer to “Fabric State Changes” on page 15.
• Switch Resource: Refer to “Switch Resource” on page 15.
• Traffic Performance: Refer to “Traffic Performance” on page 16.
• FCIP Health: Refer to “FCIP Health” on page 17.
When a category contains an “out-of-range” error, the dashboard displays a table showing the rules
triggered in that category since the previous midnight. This allows you to see more precisely where
the problem is occurring. Each category in the table contains the following information:
• The number of times rules were triggered in each category
• The rules that were triggered
• The number of times that a rule was triggered in the hour that it was triggered
• The entities (ports, circuits, and so on) that triggered the rule
• The values set for these entities when the rule was triggered
For each category, the dashboard stores the five most recent distinct rule violations that occurred
in each hour since the previous midnight. For each rule violation the dashboard stores the five
most recent entities on which the rules were triggered. Consequently, while a rule might be
triggered multiple times within a given hour, only the timestamp of the latest violation is stored,
along with the last five entities on which the rule was triggered. However, each violation of a rule
individually is reflected in the “Rule Count” for that category and the “Repeat Count” for that rule in
that hour.
For example, if the same rule was triggered 12 times in one hour, the “Repeat Count” value for that
rule will be 12, but only the timestamp for the last occurrence is displayed. In addition the last five
distinct entities on which this rule was triggered are stored (and these can include different
instances of the rule’s violation). Alternatively, if a rule was triggered 12 times since midnight, but
each violation happened in a different hour, then each violation is logged separately in the
dashboard.
Historical data
The historical data section provides information on how the switch has been behaving regardless of
whether rules were triggered. It contains only port-related statistics. The historical information is
the raw counter information since the previous midnight. Using this information, you can get an
idea of the errors seen on the switch even though none of the rules might have been violated. And
if you see potential issues, you can reconfigure the appropriate rule thresholds to specifically fit the
switch based on the information shown instead of using the default thresholds. The historical data
log stores the last seven days on which errors were recorded (not the last seven calendar days but
the last seven days, irrespective of any interval between these days). If a day does not have any
errors, the dashboard does not include that day in the results.