Client-Server Pairs and Protoport

Find all host protocol port information associated with the preceding 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. that match the input filters.

Properties

Node Label: Type an informative name for the Client-Server Pairs and Protoport node Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations.. You can keep the system-provided default of "Client-Server Pairs and Protoport" if you wish.

Filters

Filter the query.

Limit

Define a limit to the query.

Metrics

Specify metrics for the query to include.

Output

Show the parameters that this node receives from the preceding node in 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..

Advanced

Show an example of the JSON that is output for this data query.

Runbook Compatibility

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., On-Demand, External (Webhook), Subflow A reusable automation chunk that performs frequently used functions, such as opening a ticket in an external system, and can be used to implement integrations with third-party systems.