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.

Static inputs

A static input can be used to define global constant values that can be used anywhere in the execution chain.

Example:

{
	"trigger": { ... },
	"checks": [
	  {
			"type": "static",
			"name": "constants",
			"target": "myconstants",
			"value": {
				"threshold": 10,
				"time_period": "10s",
				"admin_lastname": "Anderson",
				"admin_firstname": "Paul"
			}
		}	],
	"actions": [ ... ]
}
Name Description
type static, defines this input as static input type
target the name under which the data is available in later execution steps.
value An object defining the constants.

Accessing static input data in the execution chain

In this example, the constant values defined in the value section can be accessed in later execution steps. Examples:

Usage in a trigger:

	"trigger": {
		"schedule": {
			"interval": ""
		}
	}

Usage in an action:

"actions": [
  {
    ...
    "email": {
      ...
      "body": "Dear . There are too many errors in the system, see attached data"
    }
  }
]

Not what you were looking for? Try the search.