Limits

Data query A runbook node category that gets data about the trigger and forwards it to other nodes in the runbook for further processing. nodes Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. in a 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. can return many entities Things deployed in the customer environment that are needed to run the business, such as applications, devices, interfaces, and locations. (applications An entity type representing software applications deployed in the customer environment that are monitored for performance and anomalies., devices An entity type representing network devices or hardware components deployed in the customer environment that are monitored for performance and anomalies., interfaces An entity type representing network interfaces on devices that are monitored for performance metrics and anomalies., and so on). Without a limit, the query might return more than you need or more than downstream nodes handle well. The Limits section lets you cap how many entities the query returns and how the query chooses them: by a specific metric A measurement or data point that is monitored and analyzed to detect anomalies and generate incidents. over a time interval. This topic describes the Limit controls you see in the Runbook Editor on data query nodes. For filters that narrow which entities are in scope, see Filters. For the list of metrics and how they are used, see metric definitions.

Where you configure limits

In the Runbook Editor, select a data query node and open its properties. The Limit section appears when the node type requires it. Typically, the Limit section appears when the query can return a large set of entities and you must constrain the result. Not every data query node shows the Limit section. It depends on the node’s filters and object type. When limits appear, you see three controls: Limit To, Based On, and Over The Last. For an overview of data query properties, see Data Query Properties.

Limit To

Limit To is a number that sets the maximum number of entities the query returns. For example, "Limit To 10 applications" returns at most ten applications. The default is ten. You can enter a different positive integer. The query returns the "top" entities according to the metric and direction chosen in Based On over the time interval in Over The Last.

Based On

Based On is a dropdown that selects the metric used to rank and select the top entities. The list comes from the metrics supported by that node’s object type (for example throughput, response time, or other metrics). The query sorts entities by this metric (in the direction defined in the metadata, usually descending so the highest values are first) and then takes the first N, where N is the Limit To value.

Over The Last

Over The Last is a dropdown that sets the time interval the query looks back over for the selected metric. Typical options include 15 minutes, 30 minutes, one hour, and longer (for example 24 hours or more), depending on the node type. The query uses the same duration for the limit ranking and for the metric data the node returns. Duration options can vary by object type.

Related information

Data Query Properties links to all data query property topics, including Filters and Metric Collection. How Filtering Works in Runbook Nodes explains how filter values are supplied. Runbook Editor and Using the Runbook Editor describe building and editing runbooks.