In USM you can create a custom alarm view for alarm filters to provide quick views into specific data. For example, you can create an alarm filter that shows only disk alarms at or above critical or that shows only alarms with certain hostname components.
I'm building a USM Custom alarm view , what possible fields can I add as column? In the USM Custom view options we don't have the same field possible as in the USM "edit columns". Why I cannot add the column "Aknowledged" and "Aknowledged_at" ?
• The documentation mentions provides some examples, specifically for columns:
- <col> = [hostname, message, time_last, subsys, sid, count, time_origin, source, origin, probe, nas, robot, hub, domain, dedicated, os_type, os_name, assigned_to, assigned_by, assigned_at, user_tag_1, user_tag_2, custom_[1-5], note, vis]
This is only an example. This is not a list of all available fields. Actually, additional fields can be added. For example: " acknowledged_by'
• However, not all fields can be added.
In USM alarm view > Actions > you can manually add the visible columns as in the list below:
Some of these cannot be added to a Custom View.
The value "Aknowledged" and "Aknowledged_at" cannot be added.
This is because they are not fields of the NAS_ALARMS.
These are "named" column and, in the Database, they correspond to:
Aknowledged = true (Means the alarm is not in the NAS_ALARMS as it was closed)
Aknowledged = false (Means the alarm is the NAS_ALARMS as it open)
Aknowledged_at = closed.time in the NAS_TRANSACTION_SUMMARY
With the configuration flags in the custom view, you are calling directly data from the NAS_alarms. "assigned" and "assigned_at" (they don't actually exist "as such" in the database) will not show when you add those flags.
Also, these 2 values, are never populated if you are only visualizing only open alarms. You only see these columns populated with data when showing "historic alarms". Therefore, to populate those fields you would, in any case, need manual intervention to show historical alarm first.