As information from various end points is consumed into MachineShop, it can be analyzed in real-time for specific events or conditions that may be of interest. Instead of managing a flood of non-actionable data, Rules and Event Management services allow control over the conversion of your inbound data to actionable information.
Rules and events are defined via simple RESTful service calls to Rules and Event Management services. These APIs include methods that enable the application to completely define their operation. Using standard JSON language, a rule can be established that will inspect any data element that is contained within any report from any endpoint. The rules can be defined using normalized JSON data structures that are created by our data collection service.
Complex rule conditions can be created by defining dependent rules. These special rule types allow for making a specific rule dependent on a previously defined rules trigger. This provides maximum flexibility in creating customer specific actionable information.
Rules and Event Management service rules can have a variety of actions, from simple user notifications to complex application notification methods. Actions can also interact with other MachineShop services like Device and Data Source Management to change the behavior of an endpoint.
Using APIs, rules can be defined with simple if-then-else logic
Any data element from any data source can be examined in a rule, including in nested arrays using normalized dot notation
Standard logic operators supported: less than, greater than, equal, not equal
Special data operators are also supported: within, not within
Specific rules can also be defined as report time based, i.e. has reported in a given timeframe
Rule definition can contain a requirement for a previously defined rule to have been triggered
Dependent rules can also be dependent creating a deeply nested rule condition
All rules are defined via RESTful services
Rules can be queried for last status and last evaluation times
Triggered rule can report the data report causing the trigger to your application
As with all MachineShop services, each rule evaluation is recorded for transaction evaluation
A rule can apply to any specific endpoint or endpoint element accessible by the developer
Rules can be applied to one or many endpoint or entire classes of endpoint device in a single rule definition
Standard rule actions include: SMS, email, tcp, http, publish
Rule actions can also include calls to other internal or external API's
Command actions can be defined based on rule trigger in order to change endpoint behaviors