--- title: "Location Insight Metrics" slug: "location-insight-metrics" updated: 2025-10-28T15:53:32Z published: 2025-10-28T15:53:32Z canonical: "learn.servitly.com/location-insight-metrics" --- > ## Documentation Index > Fetch the complete documentation index at: https://learn.servitly.com/llms.txt > Use this file to discover all available pages before exploring further. # Location Insight Metrics Location insights can be computed by defining *Insight Metrics* for Locations. An *Insight Metric* is based on the execution of an [Algorithm](/docs/algorithms), which can be [built-in](/docs/built-in-algorithms) or a custom one. The value of an Insight Metric is automatically computed every day for each location after midnight, considering the time zone of the location, and only one value per computation period is saved. For more details, refer to the [Insights Computation](/docs/insights-computation) article. An *Insight Metric* is like any other metric, with a saved data point for each day, and the same ways to access and use historical data. ## Creating an Insight Metric To add a new *Insight Metric* for Locations, you should: 1. Enter the *Insights / Insight Metrics* page. 2. Select the Location tab. 3. Press the Add Metric button. 4. Select the Algorithm you want to use for computation. Only algorithms that have the usage equal to Location Insight Metric can be selected. 5. Press the Save button and edit the additional information. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(154).png?sv=2026-02-06&spr=https&st=2026-10-16T18%3A26%3A00Z&se=2026-10-16T19%3A26%3A00Z&sr=c&sp=r&sig=baJqqCvhhe8ivrE6nNzhhdNz1w4C0Vbhenb%2FNdN6l8g%3D) ## Editing an Insight Metric The Insight metric is described by the following sections, some of which relate to the binding of the algorithm, while others are used to configure the standard properties of the metric. ### Algorithm Reports the algorithm that was chosen, with the option to jump to its documentation (built-in) or definition (custom). ### Inputs This section allows you to configure the inputs of the selected Algorithm. Inputs can be static, where a value used for all calculations must be entered, or dynamic, where values come from, for example, a metric. For each input, according to the type, you have to configure it: - *STRING*: A text string must be provided. - *INTEGER*: An integer number must be provided. - *FLOAT*: A float number must be provided. - *BOOLEAN*: True or false must be selected. - METRIC: A thing-definition and a metric must be selected. - LOCATION METRIC: A location metric must be selected. - EVENTS: no need to be configured. - WORK SESSIONS: No need to be configured. In case there are inputs of type *METRIC*, *LOCATION METRIC*, *EVENTS,* or *WORK SESSIONS*, in addition, you can specify the *Date Range* to be extracted and passed to the Algorithm (e.g., Last 24 hours). The end instant of the selected date range always refers to past midnight relative to the time at which the insight [computation](/docs/insights-computation) takes place. In case there are inputs of type METRIC, the Algorithm will receive as input the data of all the things having the selected metric and inheriting from the selected thing-definition. ### Output This is the Algorithm output to be read once executed and saved as the value of the metric. By changing the output, also other metric properties may change, for instance, the Name, the Value Type, and the relative Dictionary or Ranges. ### General This section allows defining the basic metric information. - **Label:** the label displayed in the DPS pages. - **Name**: the name of the metric, also used to reference it within the page templates. - **Description**: the text describing the metric and displayed as a tooltip within the pages. - **Unit**: the unit of measurement (e.g., Kg, °C, pieces, liters...etc.) - **Value Type**: the type of the metric values, one of *Boolean, Double, Float, Integer, Long, or String.* > The type is automatically selected according to the chosen Algorithm output type. - **Group**: the group the metric belongs to (e.g. Temperatures, System). Used to organize and search metrics in the console, and used by widgets in the DPS. ### Computation Period The period used to compute the insight metric and save samples, possible values are: 1 Day, 1 Month, 1 Year. For more details, refer to the [Insights Computation](/docs/insights-computation) article. ### Data In case of numeric metrics, the Data Type allows you to define whether the metric values are *DISCRETE* or *CONTINUOUS*, and then you can also define [Dictionary and Thresholds](/docs/dictionary-and-thresholds-1). ### Range In case the metric is of type numeric, in this section, you can specify the minimum and maximum values the metric can assume. Minimum and maximum values can also be dynamically redefined by specifying a property or a metric for them. In case you are using a dynamic range, remember to specify a static range that at least contains the dynamic one. These values are used to define thresholds (*CONTINUOUS data type)*, and are used in widgets to display additional information: - [Radial Gauge](/docs/radial-gauge-widget): displays the minimum and maximum values on the dial. - [Time Series Chart](/docs/time-series-chart-widget) : displays the lines for the minimum and maximum limits. ### Reset - **Manual Reset**: if checked, the metric can be manually reset from the [Location Details](/docs/location-details-widget) widget. - **Reset Value**: the value to be saved when a reset occurs. - **Editable Reset Value**: if checked, when the user resets the metric, the reset dialog allows providing the new value. The provided value is validated according to the configured range (Min and Max values). ## Try Insight Computation Once you have configured the algorithm you want to use for computing the Insight, you can test its execution by using the *Try Insight Computation* button. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(155).png?sv=2026-02-06&spr=https&st=2026-10-16T18%3A26%3A00Z&se=2026-10-16T19%3A26%3A00Z&sr=c&sp=r&sig=baJqqCvhhe8ivrE6nNzhhdNz1w4C0Vbhenb%2FNdN6l8g%3D) By clicking on the button, a pop-up allows you to select the Customer, and a Location where to test the execution. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(156).png?sv=2026-02-06&spr=https&st=2026-10-16T18%3A26%3A00Z&se=2026-10-16T19%3A26%3A00Z&sr=c&sp=r&sig=baJqqCvhhe8ivrE6nNzhhdNz1w4C0Vbhenb%2FNdN6l8g%3D) When the context has been provided, you can push the Try button to execute the algorithm. The next page will show you the Result and Logs. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(157).png?sv=2026-02-06&spr=https&st=2026-10-16T18%3A26%3A00Z&se=2026-10-16T19%3A26%3A00Z&sr=c&sp=r&sig=baJqqCvhhe8ivrE6nNzhhdNz1w4C0Vbhenb%2FNdN6l8g%3D)