--- title: "Event Trigger Conditions" slug: "event-trigger-conditions" updated: 2026-06-11T15:15:58Z published: 2026-06-11T15:15:58Z canonical: "learn.servitly.com/event-trigger-conditions" --- > ## Documentation Index > Fetch the complete documentation index at: https://learn.servitly.com/llms.txt > Use this file to discover all available pages before exploring further. # Event Trigger Conditions On the event definition page, it is possible to configure the conditions driving when the event is to be activated or cleared. ## Condition Types When configuring a condition, it is necessary to first select the condition type, which affects the way it is defined and the information involved. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(128).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A19%3A42Z&se=2026-10-16T18%3A19%3A42Z&sr=c&sp=r&sig=93TFOteYT0K%2BazWIOXc%2B2zFFMm%2Fj8kR3DI01QIGCstg%3D) Each type has its own configuration form, allowing you to select metrics, properties, or other events. ### User Reported Events with this type of condition must be reported by the user directly in the DPS, or via API requests. Only these event types support this condition type: - **Failure, Anomaly or Operation:** can be reported by using the Report Event button in the [Event List](/docs/event-list-widget) widget. - **Maintenance***:* can be reported by using the *Add Maintenance Activity* button in the [Maintenance Registry](/docs/maintenance-registry-widget) widget. - **Work Session**: can be created by using the *Create Work Session* button in the [Historical Work Session List](/docs/historical-work-session-list-widget) widget. There is no other information to specify for this type of condition. ### Simple You can select a metric or a property, a predicate, and specify a comparison value which can be: - static (e.g. Temperature 1 > 100 °C) - read from another metric (e.g. Temperature 1 > Temperature 2) - read from a property (e.g. Temperature > thing.properties.maxTemperature). ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(130).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A19%3A42Z&se=2026-10-16T18%3A19%3A42Z&sr=c&sp=r&sig=93TFOteYT0K%2BazWIOXc%2B2zFFMm%2Fj8kR3DI01QIGCstg%3D) ### Simple on Binary Value Other than comparison predicates (e.g. greater than, equal) you can use the *Bit at Position* predicate which, starting from a binary encoded value (INTEGER, HEX), allows checking the BIT at a specific position (big-endian). When the BIT is 1, the event is considered active; otherwise it is cleared. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(131).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A19%3A42Z&se=2026-10-16T18%3A19%3A42Z&sr=c&sp=r&sig=93TFOteYT0K%2BazWIOXc%2B2zFFMm%2Fj8kR3DI01QIGCstg%3D) The used binary encoding is automatically detected according to the metric type: - **Integer, Long**: the binary encoding of the metric value is INTEGER. - **String**: the binary encoding of the metric value is HEX. This predicate is available in Active conditions only. ### Simple on Date Value When selecting *Property* as left operand, you can select a property of type DATE and use the following predicates: - **Expired by N Days***:* evaluates whether the date is expired by a specific number of days. - **Expired by N Hours***:* evaluates whether the date is expired by a specific number of hours. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(132).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A19%3A42Z&se=2026-10-16T18%3A19%3A42Z&sr=c&sp=r&sig=93TFOteYT0K%2BazWIOXc%2B2zFFMm%2Fj8kR3DI01QIGCstg%3D) A negative value allows the event to be activated in advance of the date. ### Expression You can select one or more metrics and properties and combine values into a boolean expression. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(133).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A19%3A42Z&se=2026-10-16T18%3A19%3A42Z&sr=c&sp=r&sig=93TFOteYT0K%2BazWIOXc%2B2zFFMm%2Fj8kR3DI01QIGCstg%3D) In addition, you can define multiple conditions to implement an IF-ELSE-IF logic. This option is available only for *Failures*, *Anomalies* and *Operations* events. ### Event Based It is possible to select another event and define a condition based on its activation frequency. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(134).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A19%3A42Z&se=2026-10-16T18%3A19%3A42Z&sr=c&sp=r&sig=93TFOteYT0K%2BazWIOXc%2B2zFFMm%2Fj8kR3DI01QIGCstg%3D) This option is available only for *Anomalies* events. ### Wear The event is automatically updated according to the status of a wear metric. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(135).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A19%3A42Z&se=2026-10-16T18%3A19%3A42Z&sr=c&sp=r&sig=93TFOteYT0K%2BazWIOXc%2B2zFFMm%2Fj8kR3DI01QIGCstg%3D) For more details, refer to the [Wear Metrics](/docs/wear-metrics) article. This option is available only for Anomalies and Operation events. ## Event Computation Limits For any type of event with an automatic activation condition, you can select the **Limit this event computation on a specific time period** checkbox, and define the Start and End day of the year when the event can be activated. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(136).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A19%3A42Z&se=2026-10-16T18%3A19%3A42Z&sr=c&sp=r&sig=93TFOteYT0K%2BazWIOXc%2B2zFFMm%2Fj8kR3DI01QIGCstg%3D) ## Minimum Active Time In addition, for events of type Failure, Anomaly, or Operation, you can specify the *Minimum Active Time* the condition must remain true before activating the event. This makes it possible to discard all cases in which the active condition is triggered for a short time, but the event is not yet to be recorded. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image-Z1FA44VL.png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A19%3A42Z&se=2026-10-16T18%3A19%3A42Z&sr=c&sp=r&sig=93TFOteYT0K%2BazWIOXc%2B2zFFMm%2Fj8kR3DI01QIGCstg%3D) ## Minimum Reactivation Timeout When an event is configured to activate as soon as a metric crosses a threshold, a metric that hovers near that threshold can repeatedly cross it in a short time, generating a burst of alerts. To avoid the too-many-notifications syndrome, you can now define a *Minimum* *Reactivation* *Timeout:* once the event activates, it will not be reactivated again until the configured time has elapsed. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image-PUIO4CQO.png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A19%3A42Z&se=2026-10-16T18%3A19%3A42Z&sr=c&sp=r&sig=93TFOteYT0K%2BazWIOXc%2B2zFFMm%2Fj8kR3DI01QIGCstg%3D) This lets you limit the events, for example, to at most one per hour, keeping notifications meaningful and avoiding alert fatigue for the people monitoring the products. ## Instantaneous Events Within the active condition, you can select whether the event is instantaneous. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(749).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A19%3A42Z&se=2026-10-16T18%3A19%3A42Z&sr=c&sp=r&sig=93TFOteYT0K%2BazWIOXc%2B2zFFMm%2Fj8kR3DI01QIGCstg%3D) An instantaneous event is an event that occurs at a single point in time, with no duration. It is triggered by a signal, typically a single bit or state change, and is immediately considered completed once activated. These events can be used to capture specific occurrences like a system reset, an alarm trigger, or a machine operation, and are instantly stored in the event history without the need for a separate clearing condition.