> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/service-reliability-management/use-srm/monitored-services/health-source/azurelogs.md).

# Configure Azure Log Analytics as a health source

In Harness, a health source is a mapping of a Harness service to a service running in a deployment environment that is being monitored by an Application Performance Monitoring (APM) or logging tool. This mapping allows Harness to collect metrics and data from the APM or logging tool and use it to determine the health and status of the service in Harness.

This topic describes how to set up Azure Log Analytics as a health source in a monitored service.

### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

* An Azure Log Analytics connector has been added to the Harness platform.
* A monitored service has already been created in the Harness SRM.

### Add Azure Log Analytics health source <a href="#add-azure-log-analytics-health-source" id="add-azure-log-analytics-health-source"></a>

To add Azure Log Analytics as a health source:

1. In the **Health Sources** section, select **Add**. The Add New Health Source dialog appears.
2. On the **Define Health Source** tab, do the following:
   1. In the **Define Health Source** section, select **Azure Log Analytics** as health source type.
   2. In the **Health Source Name** field, enter a name for the health source.
   3. In the **Connect Health Source** section, select the **Select Connector**.\
      The Create or Select an Existing Connector dialog appears.
   4. Select a connector for the Azure Logs health source and then select **Apply Selected**.\
      The selected connector appears in the **Select Connector** dropdown field.
   5. In the **Select Feature**, you can either select **Azure Log Analytics**\*.
   6. Select **Next**.\
      The **Configuration** tab appears.

#### Define metric and log configuration settings <a href="#define-metric-and-log-configuration-settings" id="define-metric-and-log-configuration-settings"></a>

Perform the following steps based on the feature you have selected in the **Select Feature** field.

**Steps to configure Azure Cloud Metrics in Azure Log Analytics**

1. On the **Configuration** tab, select **Add Metric**.\
   The Add Metric dialog appears.
2. Enter the following information and then select **Submit**:
   * **Metric name**: Enter a name for the metric. For example, Memory Metric.
   * **Group name**: If the group where you want to add the metric already exists, select it.\
     If you want to create a new group, select **Add New**. In the **Add Group Name** settings, enter a group name, and then select **Submit**.
3. In the Add Metric dialog, select **Submit**.

The new group and metric are created. The query specifications and mapping settings are displayed. These settings help you get the desired metric data from the Azure Log Analytics platform and map it to a Harness service. To learn about Azure Log Analytics and queries, go to [Azure Monitor Logs](https://learn.microsoft.com/en-us/azure/azure-monitor/logs/data-platform-logs).

**Define a query**

1. **Resource ID** - the Azure resource Id you wish to target for the query,
2. **Metric namespace** - the Azure metric namespace you want to target for the query.
3. **Metric name** - The name of the metric you wish to query on.
4. **Aggregation** - Aggregations allow you to summarize raw log data to create more compact, meaningful, and actionable information. You can perform calculations such as counting, summing, averaging, minimum, and maximum on numeric data, and you can also perform operations like counting unique values or grouping data by specific attributes.
   * Average
   * Maximum
   * Minimum
   * Total
   * Count

{% hint style="info" %}
You can find the values necessary for each query using the Azure UI. Generally you need to follow these steps:

1. Select the [Azure Metric](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/analyze-metrics) you want to analyze.
2. Click on the [`Share` option](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/analyze-metrics#share-your-charts) in the dashboard and select `Copy Link`.
3. Input your URL into a [URL decoder](https://meyerweb.com/eric/tools/dencoder/). This should result in you seeing a JSON payload.
4. In the JSON payload you decoded, you should be able to find the **resource ID**, **metric namespace**, and **metric name**.
   {% endhint %}

**Assign services**

In the **Assign** section, select the services where you want to apply the Azure Logs metric. Following options are available:

* **Continuous Verification (applied to pipelines in Continuous Deployment)**: Select this option to use the metric data in the Continuous Deployment pipeline to ensure that the deployed service is running safely and to perform automatic rollbacks. In addition, the metric will be used to apply machine learning in detecting and highlighting future deployment issues.
* **Service Health**: Select this option to use the metric data to track the changes in the health trend of your monitored service.
* **Service Level Indicator (SLI)**: Select this option to use the metric data to measure the SLI and obtain the performance of the service.

**Configure risk profile**

If you select **Continuous Verification (applied to pipelines in Continuous Deployment)** or **Service Health**, expand the section below and follow the instructions for configuring the risk profile.

**Risk Profile**

{% hint style="info" %}
The **Risk Profile** section is only visible if you have selected **Continuous Verification (applied to pipelines in Continuous Deployment**) or **Service Health** in the **Assign** section.
{% endhint %}

1. Under **Risk Category**, select one of the following options:

* **Errors**
* **Infrastructure**
* **Performance/Throughput**
* **Performance/Other**
* **Performance/Response Time**

2. Under **Deviation Compared To Baseline**, select the following settings to measure your service's behavior and calculate deviations from the health source:

* **Higher counts = higher risk**
* **Lower counts = higher risk**

{% hint style="info" %}
You can select multiple options.
{% endhint %}

**Map service instance identifier**

{% hint style="info" %}
The **Map service instance identifier** section is only visible if you have selected **Continuous Verification (applied to pipelines in Continuous Deployment**) in the **Assign** section.
{% endhint %}

In **Service Instance Identifier (only needed for CV)**, specify the service instance identifier, which represents a dynamically created service that you deploy using Harness. The default value is `_sourceHost`.

**Advanced (Optional)**

{% hint style="info" %}
The **Advanced (Optional)** section is only visible if you have selected **Continuous Verification (applied to pipelines in Continuous Deployment**) in the **Assign** section.
{% endhint %}

**Ignore Thresholds**

You can select the types of events that you want to set thresholds for in CV. Metrics that match the selected rules will not be flagged as anomalous, regardless of the analysis.

To set the **Ignore Thresholds** for CV:

1. Go to the **Ignore Thresholds** tab and select the **Add Threshold** button.
2. From the **Metric** dropdown, select the desired metric for which you want to set the rule.
3. In **Criteria**, choose the type of criteria you want to apply for the threshold:

* **Absolute Value**: Select this option and enter the **Greater than** and **Lesser than** values.
* **Percentage Deviation**: Select this option and enter the **Lesser than** value.

**Fail-Fast Thresholds**

You can select the type of events for which you want to set thresholds in CV. Any metric that matches the selected rules will be marked as anomalous and cause the Workflow state to fail.

To set fail-fast thresholds for CV, follow these steps:

1. Go to the **Fail-Fast Thresholds** tab and select the **+ Add Threshold** button.
2. From the **Metric** dropdown, select the desired metric for which you want to set the rule.
3. In the **Action** field, select what the CV should do when applying the rule:

* **Fail Immediately**
* **Fail after multiple occurrences**
* **Fail after consecutive occurrences**

4. In the Count field, set the number of occurrences. This setting is only visible if you have selected **Fail after multiple occurrences** or **Fail after consecutive occurrences** in the **Action** field. The minimum value must be two.
5. In the Criteria field, choose the type of criteria you want to apply for the threshold:
   * **Absolute Value**: Select this option and enter the **Greater than** and **Lesser than** values.
   * **Percentage Deviation**: Select this option and enter the **Lesser than** value.

**Steps to configure Azure Analytics Cloud Logs in Azure Log Analytics**

1. On the Configuration tab, select **+ Add Query**.\
   The Add Query dialog appears.
2. Enter a name for the query and then select **Submit**.\
   The Custom Queries settings are displayed. These settings assist in retrieving the desired logs from the Azure Logs platform and mapping them to the Harness service. To learn about Azure Logs logs, go to [Azure Monitor Logs](https://learn.microsoft.com/en-us/azure/azure-monitor/logs/data-platform-logs).

**Define a query**

1. In **Resource Id / Workspace Id**, enter the Azure Resource Id or Workspace Id you want to target.
2. In the **Query** field, enter the log query and select **Run Query** to execute it. This displays a sample record in the **Records** field, allowing you to confirm the accuracy of the query you've constructed.
3. In the **Field Mapping** section, select the **Service Instance Identifier** to display the logs, and then select **Get sample log messages**. Sample logs are displayed that help you verify if the query you built is correct.

#### Save the health source settings <a href="#save-the-health-source-settings" id="save-the-health-source-settings"></a>

1. After configuring all the settings, select **Submit**. The Azure Logs health source gets added to the monitored service.

FEEDBACK\_BUTTON