[Backlogmanager] [FIWARE-JIRA] (HELP-18481) FIWARE.Question.Tech.How to define Alarm Events in Fiware entities (NGSI).

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-18481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez reassigned HELP-18481:
-------------------------------------

    Assignee: Backlog Manager

> FIWARE.Question.Tech.How to define Alarm Events in Fiware entities (NGSI).
> --------------------------------------------------------------------------
>
>                 Key: HELP-18481
>                 URL: https://jira.fiware.org/browse/HELP-18481
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Backlog Manager
>              Labels: fiware, fiware-orion
>
> Created question in FIWARE Q/A platform on 04-10-2021 at 16:10
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/69439304/how-to-define-alarm-events-in-fiware-entities-ngsi
> +Question:+
> How to define Alarm Events in Fiware entities (NGSI)
> +Description:+
> Is there any common practise to define alarm events in Fiware data model entities? I mean if we have devices sending alarm events like for example if we currentTooHigh. Something like this:
> "currentTooHigh": {
> "type": "Text",
> "value": "off",
> "metadata": {
> "dateStarted": {
> "type": "DateTime",
> "value": "2021-09-18T12:02:49.000Z"
> }
> "dateUpdated": {
> "type": "DateTime",
> "value": "2021-09-18T16:02:49.000Z"
> }
> }
> perhaps also add a some severity attribute as metadata , like info, warning, error and failure. etc.. or something
> I am asking how it is already being done so I do not have to make something up new.



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)