> 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/continuous-delivery/use-continuous-delivery/verify-deployments/configure-cv/health-sources/splunk.md).

# Splunk

Learn how to set up Splunk as a health source for CV

### Before you begin <a href="#before-you-begin" id="before-you-begin"></a>

This page assumes you have followed the rest of the steps to set up CV. To learn more, go to [Configure CV](/continuous-delivery/use-continuous-delivery/verify-deployments/configure-cv/verify-deployments.md)

Additionally, [add Splunk as a verification provider](/harness-ai/use-harness-platform/connectors/monitoring-and-logging-systems/connect-to-monitoring-and-logging-systems.md)

### Step 5: Add Health Sources <a href="#step-5-add-health-sources" id="step-5-add-health-sources"></a>

This option is available only if you have configured the service and environment as fixed values.

A Health Source is basically a mapping of a Harness Service to the service in a deployment environment monitored by an APM or logging tool.

1. In **Health Sources**, click **Add**. The **Add New Health Source** settings appear.

   ![](https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-9856c3fca7b06e965d1f15ef3e75f907b3884e92%2Fverify-deployments-with-splunk-38.png?alt=media)
2. In **Select health source type**, select Splunk.
3. In **Health Source Name**, enter a name for the Health Source.
4. Under **Connect Health Source**, click **Select Connector**.
5. In **Connector** settings, you can either choose an existing connector or click **New Connector.** ![](https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-7526a3b7799794c663724bd286a419232d12c26a%2Fverify-deployments-with-splunk-39.png?alt=media)
6. Click **Apply Selected**. The Connector is added to the Health Source.

   ![](https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-7abdb2eee22781b02b547febc9e74d36d28cd4a0%2Fverify-deployments-with-splunk-40.png?alt=media)
7. In **Select Feature**, select the Splunk feature to be used.
8. Click **Next**. The **Customize Health Source** settings appear. The subsequent settings in **Customize Health Source** depend on the Health Source Type you selected. You can customize the metrics to map the Harness Service to the monitored environment in **Query Specifications and Mapping** settings.

   ![](https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-03dd9f771314911b7f0441f58d59995ff63f75d5%2Fverify-deployments-with-splunk-41.png?alt=media)
9. Click **Map Queries to Harness Services** drop down.
10. Enter a name for the query in **Name your Query**.
11. Click **Select Query** to select a saved query. This is an optional step. You can also enter the query manually in **Query**.
12. Click **Fetch Records** to retrieve the details. The results are displayed under **Records.** ![](https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-a077859bc0ba408b65f1163a32305b8b135f6685%2Fverify-deployments-with-splunk-42.png?alt=media)
13. Once the records are fetched, click the plus icon in **Identify Service Instance** to select the path for service instance.
14. Click **Submit**. The Health Source is displayed in the AI Verify (v1) step.

![](https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-88ced93d43cfd8b7788ac2b69995615c2a703012%2Fverify-deployments-with-splunk-43.png?alt=media)

You can add one or more Health Sources for each APM or logging provider.

{% @harness-feedback/feedback %}