Any entity including groups, nodes, endpoints/interfaces and links can have alarms. These alarms propagate up the hierarchy of groups so that you can always find impacting issue even from a high-level.
Here we can see the ‘S3’ group has been expanded to show S3 buckets.
Some of these buckets have alarms as indicated by the colored halo around those nodes.
We can also see these alarming nodes in the 'ALARMS' tab of S3 group:
At either a group or node level you can disable all alarms for a timed duration (or forever):
This will suppress the alarm halos around nodes in the 3D view and they will not appear to be in a bad state as far as the 3D map is concerned.
The fact that these nodes have alarms will still be indicated in the 'ALARMS' tab but they will be shown with a grey severity of 'DISABLED' to indicate that they have been manually disabled:
After the specified time-frame elapses the alarms will be re-enabled automatically. You can also manually re-enable alarms by revisiting the ALARMS tab of the node or group that you used to perform the disablement.
'Muting' specific types of Alarms on specific entities
It is also possible to 'mute' only certain types of alarms for a specific entity.
Unlike disablement which can be applied at a group level to apply to all nodes within it, muting is far more granular - you must choose a specific entity you wish to configure and then select a type of alarm you wish to mute for this entity:
Like disabled alarms, muted alarms are suppressed from manifesting in the 3D map. They do however still show up on the ALARMS tab but their severity is replace with a grey severity of 'MUTED' to indicate that they have been manually muted:
You can also manually re-enable alarms by revisiting the ALARMS tab of the node or group that you used to perform the muting.