Alarm queries
- Last UpdatedOct 09, 2024
- 1 minute read
The AlarmApp supports standard Galaxy alarm query formats, such as:
\galaxy!Area_001
Alarm query syntax is the same for both Current Alarms Mode and Recent Alarms and Events Mode. Queries in Historical Alarms, Historical Events, and Historical Alarms and Events modes are actually Alarm Database queries, which follow rules and syntax for SQL Server database queries.
The AlarmApp also supports relative references for Galaxy alarms in alarm queries. For all alarm modes, relative references are resolved at run time at the point of query to the Alarm Manager or Alarm Database.
You must put the reference part of the alarm query between less-than (<) and greater-than (>) characters.
The following table shows examples of alarm queries.
|
Alarm Query |
Description |
|---|---|
|
\provider!group |
Shows all alarms from the given provider and group. Example \intouch!Group_A |
|
\provider!group!tagname |
Shows all alarms from the given provider, group and tag. Example \galaxy!Mixing_Area!RotorCtrl |
|
\\node\provider!group |
Shows all alarms from the given provider and group from a given node. Example \\remote\intouch!Group_B |
|
\\node\provider!group!tagname |
Shows all alarms from the given provider, group and tag from a given node. Example \\grnode\galaxy!Packaging_Area!Wrapper1 |
|
\galaxy!<Area>!<tagname>.* |
Shows all alarms from the Automation Object. Alarms from other Automation Objects in the same area are ignored. |
|
\galaxy!<myArea.tagname> |
Shows all alarms from the Area object hosting the Automation Object |
|
\galaxy!<myPlatform.tagname> |
Shows all alarms from the Winplatform object hosting the Automation Object. |
|
\galaxy!<myEngine.tagname> |
Shows all alarms from the AppEngine object hosting the Automation Object. At run-time the AlarmApp resolves the myEngine attribute to detect the host. |