Version: 7.x-36.0.0

This is a technical preview. Technical preview features are not fully supported, may not be functionally complete, and are not suitable for deployment in production. We encourage you to try them out and provide your feedback, good and bad, on the Search Guard forum. This will help us improve and add any features you might be missing.

Creating triggers

What is a trigger

Every watch has to define a trigger. A trigger specifies when a watch gets executed (“triggered”). Currently the following trigger types are supported:

  • Date and time
    • for example, every Wednesday at 2pm
  • Interval
    • for example, every 10 minutes
  • cron
    • gives you the full power of cron expressions

Example:

{
	"trigger": {
		"schedule": {
			"weekly": {
				"on": "thursday",
				"at": "14:40:45"
			}
		}
	},
	"checks": [ ... ],
	"actions": [ ... ]
}

Trigger execution

Each trigger gets registered with the Trigger Execution Engine. The execution engine makes sure that

  • Each trigger is executed on exactly one node at a time
    • You can specify node filters to define on which nodes Signals Alerting should run
  • Triggers created in different tenants will not interfere whith each other

Time zones

Signals supports different time zones. If no time zone is specified, the default JVM time zone is used.


Not what you were looking for? Try the search.