User Device Node (Deprecated)

This nodeClosed Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. has been deprecated. The node will no longer be able to be added to runbooksClosed 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., but will be visible in any runbook where it has already been used. The same functionality is now available in the Data Store node.

Find user devicesClosed An entity type representing network devices or hardware components deployed in the customer environment that are monitored for performance and anomalies. and their relevant metricsClosed A measurement or data point that is monitored and analyzed to detect anomalies and generate incidents..

By default, this node collects and forwards these metrics for user devices:

  • Business Location

  • User Device Name

  • User Name

  • User Device ISP

  • Physical Location

  • Physical Location City

  • Physical Location State

  • Physical Location Country

  • User Connection Type

  • WiFi BSSID

  • WiFi Channnel

  • WiFI SSID

Properties

Node Label: Type an informative name for the User Device node. You can keep the system-provided default of "User Device" 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.

Advanced

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

Runbook Compatibility

IncidentClosed 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), SubflowClosed 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.