Triggers

Manufactory supports (almost) real-time triggers and we sometimes call them event-based triggers.

This is unique - because many other systems don’t give you the ability to act quickly on incoming data patterns.

Event-based triggers fire based on actor actions. For example, a trigger could be set up to fire when an actor logs in or logs out, or when an actor takes a specific action within a system or application with or without a specific time-frame or even a specific occurrence count.

A Manufactory trigger includes:

• A condition is a specific rule or set of rules that must be met for the trigger to fire.
• A criteria is a specific set of conditions that must be met for the trigger to be executed.

Conditions can be based on various factors, like actor actions, system events or updating actor’s attributes. For example, a condition could be set up to trigger a notification when a certain amount of time has passed since an actor last logged into an application, or when a specific event is stored.

Criteria, on the other hand, are a set of conditions that must be met for the trigger to be executed. For example, a criteria could be set up to trigger an alert when a user logs in from an unrecognized device and is trying to access sensitive data. In this case, the criteria could include conditions like the user’s location, the type of device being used, and the time of day.

For additional information about triggers, contact us

Related articles

Overview

Tallyfy Manufactory is a scalable API-based events lifecycle engine that handles event collection querying and triggering for authenticated users while allowing organizations to maintain control over their own analytics and visualization capabilities as a cost-effective alternative to comprehensive platforms.

Manufactory > Use cases and internal use with Tallyfy Pro

Tallyfy Manufactory serves as an event lifecycle management system that integrates with Tallyfy Pro to enable automated workflow triggering based on real-time events predictive maintenance scheduling and enhanced operational visibility through event-driven task assignments and dynamic process adjustments.

Best Practices > What is observability?

Observability enables deep understanding of complex systems through detailed event data analysis to explore and debug both known and unknown issues without relying solely on predefined metrics.

Best Practices > Setting up effective alerts and SLOs

Service Level Objectives provide a user-focused alerting framework that monitors error budget burn rates to generate meaningful alerts based on actual business impact rather than arbitrary technical thresholds.