current_alerts
Differences
This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
current_alerts [2019/01/09 10:38] – created akuzmuk | current_alerts [2021/11/03 10:41] – emozolyak | ||
---|---|---|---|
Line 9: | Line 9: | ||
^Key ^Description | ^Key ^Description | ||
- | |startTime |Alert | + | |alertId|Alert |
- | |regId |The number of the register | + | |
- | |regAlias |Variable name for programs |String| | + | |
- | |bit |Number of the bit with the alarm flag |Number| | + | |
|title |Alert name |String| | |title |Alert name |String| | ||
- | |connectionTitle |Connection name |String| | + | |startTime |Alert trigger time | Number, UnixTime| |
- | |connectionId |Connection ID |Number| | + | |alertLevel |The flag indicates |
- | |connectionAlias |The name of the connection variable for programs|String| | + | |
|acknowledgedBy| User name, who confirmed the alert. If the alert is not confirmed - empty string.|String| | |acknowledgedBy| User name, who confirmed the alert. If the alert is not confirmed - empty string.|String| | ||
|acknowledgedTime |Time, | |acknowledgedTime |Time, | ||
|canBeAcknowledged |The flag indicates the alert can be confirmed. |Boolean| | |canBeAcknowledged |The flag indicates the alert can be confirmed. |Boolean| | ||
+ | |groupId|The id key of the group the alert resides in|Number | | ||
Using this structure, it is possible to implement, for example, various notification scenarios about unconfirmed accidents. | Using this structure, it is possible to implement, for example, various notification scenarios about unconfirmed accidents. |
current_alerts.txt · Last modified: 2022/07/04 12:35 by emozolyak