During operation, the machine may generate events that relate to its normal operation, but which are noteworthy to be tracked through the use of regular events.
We can have different categories of regular events:
- Information: events that normally occur during product operation, for instance, the product has started a new processing, completed a cycle, been shut down or started up.
- Advice: events that do not relate to the operation of the product, but can be used to give advice to the operator. For example, reduce the speed for a higher quality of result, or, every N processing clean the tool.
A Regular Operation event is described by:
-
Name: the name of the event (e.g. JOB_STARTED).
-
Title: the user-friendly name of the event (e.g. Job Started).
-
Description: the event description (e.g. Scheduled job T-123 started).
-
Severity: fixed to INFORMATIONAL.
-
Category: INFORMATIONAL or ADVICE.
-
Active/Clear Conditions: the metric/property-based conditions used to activate/deactivate the event instance.
In case of property-based condition, you can use only properties of type DATE. -
Notification: custom notification messages to send when the event is activated or deactivated. By default, notification messages are sent by using the event title and description, but the notification messages can be redefined, if needed.
-
Troubleshooting: a set of remedies the user can follow to fix the problem by himself.
-
Options: a set of variables that can be used to let the user customize the thresholds for event triggering.
Creating a Regular Operation
To add a new Regular Operation event, you should:
- Enter the Events / Regular Operation page.
- Select the Location or Thing Definitions tab, depending on where you want to create the event.
- In case of Thing Definition, select the Thing Definition to edit.
- Press the Add Event button.
- Provide the required information.
- Press the Save button and edit the additional information, if needed.
Editing a Regular Operation
A Regular Operation event is described by the following sections:
General
The main section describing the alert through these properties:
-
Name: specifies the name of the alert, it is a free value (e.g. TEMP WARNING).
-
Title: the alert shown title within the alert list.
-
Description: the text describing the occurred problem.
-
Severity: fixed to INFORMATIONAL.
-
Category: can be INFORMATION or ADVICE.
By selecting the Limit the alert visibility depending on the user type checkbox, it is possible to profile the alert visibility to a specific set of User Types.
By selecting the Limit this event computation on a specific time period checkbox, it is possible to define a Start and End day of the year when the event can be activated.
Within the event Title, and Description it is possible to use placeholders to include information about the thing, the event, and measures.
Dashboard
- Event Template: the template used to display the event details in a dedicated dashboard.
Active Condition
This section allows defining when the event must be activated. An event is activated only when the active condition switches its state from false to true and remains true for at least 30 seconds. In addition, you can specify the Minimum Active Time the condition must remain true before activating the event.
The Manual activation checkbox allows specifying whether the event must be manually activated by using the Manual Alert Reporting widget. Once the event has been manually activated, it can be cleared automatically by using the Clear Condition or manually by using the Clear action within the Active Alert List widget.
Clear Condition
This section allows defining when the event must be cleared.
If unspecified, the negated active condition is used instead.
Alert Activation Notification
This section allows defining the alert notification messages to be notified in case the event has been activated.
Once the status of an event is changed, users are informed in real-time through a notification by using the enabled channels (web, email, mobile push).
Servitly automatically notifies the registered users having visibility on the occurred alert, and optionally it is also possible to notify external contacts (email, SMS).
Within the notification Title, Short Message, and Long Message it is possible to use placeholders to include information about the thing, the event, and measures.
Alert Clearing Notification
This section allows defining the alert notification messages to be notified in case the event has been cleared.
Once the status of an event is changed, users are informed in real-time through a notification by using the enabled channels (web, email, mobile push).
Servitly automatically notifies the registered users having visibility on the cleared alert, and optionally it is also possible to notify external contacts (email, SMS).
Within the notification Title, Short Message, and Long Message it is possible to use placeholders to include information about the thing, the event, and measures.
Notification Delay
You can specify the delay for executing the notification to the users; if the alert is automatically cleared before the notification delay, the notification is skipped.
Technical Description and Remedies
Here you can describe more technically the event that has occurred and which are the causes and impacts. Optionally, you can provide a set of remedies, the user can follow to fix the problem by itself.
Remedies are presented to the user through the Thing Troubleshooting widget.
Options
This section allows defining options to be used within the event definition and whose value can be redefined by the end-user within the page by suing the thing-options widget.
For more details, see the Options article.
Comments
0 comments
Please sign in to leave a comment.