Mechanizations

Mechanizations is a standard configuration interface for adding, editing and removing MySQL stored procedures that are run at a scheduled time. Example mechanizations include the event correlation and the deletion of expired events.

Refer to the Standard Configuration Interface guide for details on interacting with the grid and form.

This user interface calls REST methods from api/event/mechanizations.

The UI path for this interface is Configuration -> Events -> Processing -> Mechanization.

Form Fields

Filter Clause Toolbar

Configuring Mechanization Times

Mechanizations use a cron-like syntax to determine when the mechanization is run. The scheduled time definition has a field for Minutes, Hours, Days, Months, and Days of Week. Each of these fields can be set to one or more literal value in a comma-separated list, or "*" which is interpreted as Every. The mechanization executes when the current time elements match the mechanization's scheduled time elements.

At its simplest, with every time period set to "*" (every), the mechanization will be executed every minute, because the current time will always match the mechanization's scheduled time.

However, imagine every time period is set to "*" (every) except Minutes, which are set only to 30. In this case, the current time will match the scheduled time and the application will be executed once every hour, at x:30.

It is possible to be overly complex, creating time criteria that very seldom match. Imagine a mechanization with time criteria set to Minutes="*", Hours="*", Days=26, Months=1, and WeekDay=1. That mechanization will not run until January 26, 2026 which is the next time since 2015 that January 26th will be on a Monday.

Meta

Default Mechanizations