Input Node

Specify the details an on-demand runbook needs to be able to execute. The Input node Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. requires you to explicitly supply these details to give the runbook An automated workflow that executes a series of steps or tasks in response to a triggered event, such as the detection of anomalous behavior generating an incident, a lifecycle event, or a manually executed runbook. the context it needs to be able to execute, information that an incident A collection of one or more related triggers. Relationships that cause triggers to be combined into incidents include application, location, operating system, or a trigger by itself. runbook acquires implicitly from its Trigger A set of one or more indicators that have been correlated based on certain relationships, such as time, metric type, application affected, location, or network device. node.

Properties

Node Label: Type an informative name for the Input node. You can keep the system-provided default of "Input" if you wish.

Starting Entity

Specify the object for which the on-demand runbook will execute by choosing it from the dropdown menu. This determines the Primary entity Things deployed in the customer environment that are needed to run the business, such as applications, devices, interfaces, and locations. that will need to be identified in the Run Runbook dialog when the runbook is executed.

Additional Parameter Values Received From Caller

Specify the names of variables that correspond to parameters that will be used to execute the runbook. (Each variable needs to be defined separately.) When the runbook is executed, these will be listed in the Run Runbook dialog, and each will require a value to be supplied.

Runbook Compatibility

On-Demand