# Metric Analysis

{% hint style="info" %}
Before going through this article, we recommend to learn [how to create metric templates](https://docs.opsmx.com/autopilot/analysis-setup/templates/metric-template).
{% endhint %}

The metric analysis enables customers to release software with lower risk into production. Metric data for new software updates are compared with the baseline to determine if the new software release is comparable to the software already running in production. This allows developers to determine whether the new software update is ready to be promoted to the production environment. Automation driven by this intelligence can be configured to promote the software release.

### Metric Parameters

Each metric needs to be configured based on your needs to ensure that the metric analysis produces desired results for use in automated decision-making. Important metric parameters are described as follows.

#### **Risk Direction**

Risk direction can be **Higher, Lower, or Higher & Lower**. 

* If the metric analysis has to fail if the New Release metric goes above the baseline by a certain percentage value, **use Higher**. 
* If the metric analysis has to fail if the New Release metric goes below the baseline by a certain percentage value, **use Lower**. 
* If the analysis has to fail if it goes above or below the baseline by a certain percentage value, use **Higher or Lower**.

#### Threshold(%) 

It is the percentage change beyond which the metric analysis fails. Higher and lower thresholds can be set independently for each metric.

#### Criticality 

Criticality parameters can have the following values - **Normal, Must have & Critical**. 

* The default value is **Normal**. 
* If the metric analysis has to fail if there is no metric data, select “**Must have**”. 
* If the entire analysis has to fail if this metric fails, select “**Critical**” for the metric.

**Watchlist**

Select watchlist toggle if you want the metric to appear on top of the list on the Metrics Report page.

#### NaN Strategy 

NaN strategy can have the following values - **Remove and Replace with zero**. This setting specifies how to treat missing metric values. 

* If the missing values are to be removed from the analysis, retain “**Remove**” which is the default value. 
* If the missing values are to be replaced by zeros, select “**Replace with zero**”.

#### Weight 

By default, all metrics will have a weight of 1. Metrics weight can be reduced or increased by changing this number. This will determine how the individual metric score will impact the overall metric analysis score.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.opsmx.com/opsmx-1/opsmx-context-engine/additional-resources/previous-releases/isd-3.12/data-and-intelligence-module-autopilot/autopilot/metric-analysis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.