Unified events framework

1. A computer-implemented method for detecting and managing events from data of an Internet-of-Things (IoT) network, the method being executed by one or more processors and comprising:

providing a unified events framework that is accessible to each of a plurality of enterprises operating respective IoT networks, that is agnostic to the respective IoT networks and to enterprises operating the respective IoT networks, the unified events framework comprising an event configuration component and an event ingestion framework;

storing, by the unified events framework, one or more event configurations, each event configuration being customized by an enterprise of the plurality of enterprises through the event configuration component, each enterprise associated with a respective application, each event configuration being specific to a respective event and comprising an event type, one or more statuses defining respective states of the respective event, a severity and a code associated with one of messaging and notification of the respective event;

receiving, by the unified events framework, calls from respective applications of enterprises in the plurality of enterprises, the calls comprising a first call from a first application that executes functionality specific to a first enterprise of the plurality of enterprises, the first call comprising an identifier and timeseries data from one or more IoT devices in a first IoT network, the first IoT network being exclusive to the first enterprise, the identifier identifying the first enterprise among the plurality of enterprises;

retrieving, by the event ingestion framework of the unified events framework, a rule set for processing the timeseries data, the rule set being selected from a plurality of rule sets based on the identifier; and

determining, by the event ingestion framework of the unified events framework, that an anomaly is represented in the timeseries data based on the rule set, and in response:

selecting a first event configuration from an event configuration data store of the unified events framework, the event configuration data store storing event configurations for each enterprise of the plurality of enterprises, the first event configuration being specific to the first enterprise and being distinct from a second event configuration that is specific to a second enterprise,

generating an event based on the first event configuration that defines the event,

executing an event workflow to transition the event between states, and

transmitting an event response to the first application.

2. The method of claim 1 , wherein the event is encapsulated in a package that defines the first event configuration, and comprises the event type, a property set, and a property set type of the event.

3. The method of claim 1 , wherein the event type of the event is one of mutable, and immutable.

4. The method of claim 3 , wherein during execution of the event workflow to transition the event between states, the event is mutable, and is overwritten at each state change.

5. The method of claim 3 , wherein during execution of the event workflow to transition the event between states, the event is immutable, and a new event is generated and is correlated to the event at each state change.

6. The method of claim 1 , further comprising receiving a second call from a second application that is different from the first application, the second call comprising timeseries data from one or more IoT devices in a second IoT network associated with a second enterprise that is different from the first enterprise.

7. The method of claim 1 , wherein the first application is a cloud-based application.

8. A non-transitory computer-readable storage medium coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations for detecting and managing events from data of an Internet-of-Things (IoT) network, the operations comprising:

providing a unified events framework that is accessible to each of a plurality of enterprises operating respective IoT networks, that is agnostic to the respective IoT networks and to enterprises operating the respective IoT networks, the unified events framework comprising an event configuration component and an event ingestion framework;

storing, by the unified events framework, one or more event configurations, each event configuration being customized by an enterprise of the plurality of enterprises through the event configuration component, each enterprise associated with a respective application, each event configuration being specific to a respective event and comprising an event type, one or more statuses defining respective states of the respective event, a severity and a code associated with one of messaging and notification of the respective event;

receiving, by the unified events framework, calls from respective applications of enterprises in the plurality of enterprises, the calls comprising a first call from a first application that executes functionality specific to a first enterprise of the plurality of enterprises, the first call comprising an identifier and timeseries data from one or more IoT devices in a first IoT network, the first IoT network being exclusive to the first enterprise, the identifier identifying the first enterprise among the plurality of enterprises;

retrieving, by the event ingestion framework of the unified events framework, a rule set for processing the timeseries data, the rule set being selected from a plurality of rule sets based on the identifier; and

determining, by the event ingestion framework of the unified events framework, that an anomaly is represented in the timeseries data based on the rule set, and in response:

selecting a first event configuration from an event configuration data store of the unified events framework, the event configuration data store storing event configurations for each enterprise of the plurality of enterprises, the first event configuration being specific to the first enterprise and being distinct from a second event configuration that is specific to a second enterprise,

generating an event based on the first event configuration that defines the event,

executing an event workflow to transition the event between states, and

transmitting an event response to the first application.

9. The computer-readable storage medium of claim 8 , wherein the event is encapsulated in a package that defines the first event configuration, and comprises the event type, a property set, and a property set type of the event.

10. The computer-readable storage medium of claim 8 , wherein the event type of the event is one of mutable, and immutable.

11. The computer-readable storage medium of claim 10 , wherein during execution of the event workflow to transition the event between states, the event is mutable, and is overwritten at each state change.

12. The computer-readable storage medium of claim 10 , wherein during execution of the event workflow to transition the event between states, the event is immutable, and a new event is generated and is correlated to the event at each state change.

13. The computer-readable storage medium of claim 8 , wherein operations further comprise receiving a second call from a second application that is different from the first application, the second call comprising timeseries data from one or more IoT devices in a second IoT network associated with a second enterprise that is different from the first enterprise.

14. The computer-readable storage medium of claim 8 , wherein the first application is a cloud-based application.

15. A system, comprising:

a computing device; and

a computer-readable storage device coupled to the computing device and having instructions stored thereon which, when executed by the computing device, cause the computing device to perform operations for detecting and managing events from data of an Internet-of-Things (IoT) network, the operations comprising:

providing a unified events framework that is accessible to each of a plurality of enterprises operating respective IoT networks, that is agnostic to the respective IoT networks and to enterprises operating the respective IoT networks, the unified events framework comprising an event configuration component and an event ingestion framework;

storing, by the unified events framework, one or more event configurations, each event configuration being customized by an enterprise of the plurality of enterprises through the event configuration component, each enterprise associated with a respective application, each event configuration being specific to a respective event and comprising an event type, one or more statuses defining respective states of the respective event, a severity and a code associated with one of messaging and notification of the respective event;

receiving, by the unified events framework, calls from respective applications of enterprises in the plurality of enterprises, the calls comprising a first call from a first application that executes functionality specific to a first enterprise of the plurality of enterprises, the first call comprising an identifier and timeseries data from one or more IoT devices in a first IoT network, the first IoT network being exclusive to the first enterprise, the identifier identifying the first enterprise among the plurality of enterprises;

retrieving, by the event ingestion framework of the unified events framework, a rule set for processing the timeseries data, the rule set being selected from a plurality of rule sets based on the identifier; and

determining, by the event ingestion framework of the unified events framework, that an anomaly is represented in the timeseries data based on the rule set, and in response:

selecting a first event configuration from an event configuration data store of the unified events framework, the event configuration data store storing event configurations for each enterprise of the plurality of enterprises, the first event configuration being specific to the first enterprise and being distinct from a second event configuration that is specific to a second enterprise,

generating an event based on the first event configuration that defines the event,

executing an event workflow to transition the event between states, and

transmitting an event response to the first application.

16. The system of claim 15 , wherein the event is encapsulated in a package that defines the first event configuration, and comprises the event type, a property set, and a property set type of the event.

17. The system of claim 15 , wherein the event type of the event is one of mutable, and immutable.

18. The system of claim 17 , wherein during execution of the event workflow to transition the event between states, the event is mutable, and is overwritten at each state change.

19. The system of claim 17 , wherein during execution of the event workflow to transition the event between states, the event is immutable, and a new event is generated and is correlated to the event at each state change.

20. The system of claim 15 , wherein operations further comprise receiving a second call from a second application that is different from the first application, the second call comprising timeseries data from one or more IoT devices in a second IoT network associated with a second enterprise that is different from the first enterprise.