Skip to main content

Add a metric

How the Metric Picker works and how to find the right metric when building or editing a gadget.

The Metric Picker is a pop-up window that helps you find a metric from the large number of metrics available to you. This window appears whenever you see an option to 'Add Metric' for example, when building a gadget.
​

When creating a new gadget:

While adding a new gadget to a dashboard or report, you will see the option to add a metric. This pops up the metric picker and displays a list of metrics that are available for use. You will be presented with a list of Core Metrics if they have been set up.
​

  • By default, you'll see a list of metrics from all datasets. To filter it down and see only metrics from a given dataset you can select from the list on the left.
    ​

  • Click the metric you want to select and confirm selection to add it to the gadget.
    ​

By default, you'll see a list of metrics from all datasets . To filter it down and see only


​

When editing an existing gadget:

When editing a gadget that allows adding multiple metrics such as a matrix, note that by default, we will only show datasets that are already in play i.e. datasets already in use within the gadget.
​

To pick a gadget from a different dataset, click 'Show All'.
​

To pick a gadget from a different dataset, click 'Show All'


​

Searching through the Metric Picker

If you want to quickly find metrics, but you're not quite sure what you're looking for, simply type related keywords into the search bar.
​

The search function looks for the keyword you entered across
​

  • data set name
    ​

  • field name, and
    ​

  • metric name
    ​

to give you a comprehensive list of results within the selected tab.
​

To give you a comprehensive list of results within the selected tab


​

Cannot find the metric you are looking for? Perhaps it was created as a Single Use Metric. See here to understand more about Single Use Metrics
​


​

What's next


Still using the FleetOps v1/v2 interface? View the legacy version of this article.

Did this answer your question?