> 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/monitor-deployments/using-cd-custom-dashboards.md).

# Using custom dashboards to monitor CD deployments

Monitor CD deployments using the explores that work best for you.

An Explore is a starting point for a query that is designed to explore a particular subject area. This topic describes the various tools available for monitoring CD deployments, and the data they provide. The following image shows the list of explorers available for visualizing CD data.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-60e1bd8f81de53ccb8ef27c1524fba308813833d%2Fusing-cd-custom-dashboards-1.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

Go to [Create dashboards](https://developer.harness.io/harness-platform/use-harness-platform/harness-dashboards/dashboard-legacy/create-dashboards) to get a basic overview of how to create dashboards.

## What you will learn from this topic

* How to use the [Deployments and Services](#deployments-and-services) explore and its views
* How to use the [Deployments and Services V2](#deployments-and-services-v2) explore and its views
* How to [troubleshoot](#troubleshooting) common issues with CD custom dashboards

## Before you begin

* Familiarize yourself with the explores and views described in this topic before you build a custom dashboard, since each explore exposes a different set of dimensions and measures.

### Deployments and Services <a href="#deployments-and-services" id="deployments-and-services"></a>

This exploration can be used to visualize CD data related to pipeline executions. Each explore has a set of views. The views present in this explore are:

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-9299f3768cdde642ff965c611a25108a83276366%2Fusing-cd-custom-dashboards-20.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

The following sections describe the fields and usage for each view listed above.

### Approval Stage <a href="#approval-stage" id="approval-stage"></a>

This view contains data related to the Helm manifest used in CD stage executions. The data is recorded per CD stage execution. For example, if there are 10 executions of a single service with a Helm manifest linked to it, this view will have 10 records.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-e866a14dad8b72d6fe01c7b512dc6574f720556f%2Fusing-cd-custom-dashboards-21.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

Filter-only Field:

1. Current Aggregation Period:

List of dimensions:

1. End Time: End time of the stage execution
2. Stage Name: Name of the stage
3. Stage Status: Current status of the stage(`RUNNING`/`FAILED` etc.)
4. Stage Type: Type of the stage(`Approvals`)
5. Start Time: Start time of the stage execution

List of measures:

1. Stage Execution Duration: Average stage execution duration

### Deployments <a href="#deployments" id="deployments"></a>

This view contains the data related to pipeline executions. The data is recorded per pipeline execution, meaning if there are 10 pipeline executions, then this view will also have 10 records.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-bb4c35ca86f6cec9385e1a264efba6bd18584ec7%2Fusing-cd-custom-dashboards-6.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

Filter-only Field:

1. Current Aggregation Period:

List of dimensions:

1. Deployment Duration: Duration of the pipeline execution
2. End Time: End time of the pipeline execution
3. Execution URL: URL of pipeline execution
4. Organization ID: Organization identifier where the pipeline got executed
5. Pipeline Name: Name of the pipeline
6. Project ID: Project identifier where the pipeline got executed
7. Start Time: Start time of the pipeline execution
8. Status: Pipeline status(`RUNNING`/`ABORTED`/`SUCCESS` etc.)
9. Trigger Type: Type of trigger used to execute the pipeline(`MANUAL`/`WEBHOOK` etc.)

List of measures:

1. Change Failure Rate: Total deployments that have been reverted divided by the total no. of deployments
2. Failed Deployments: The number of deployments that failed with `FAILED`/`ABORTED` statuses
3. Failure Rate: Failure rate of deployments(Failed Deployments divided by total no. of deployments)
4. Last Deployment: Last deployment time
5. Longest Deployment: Longest deployment time
6. Mean duration: Average pipeline duration
7. Mean duration trend: This compares the mean duration trend from the previous period to the current period
8. Median Duration: Median duration of the deployment
9. Success Rate: Success rate of deployments(deployments completed with `SUCCESS` status)
10. Total Deployments: Total no. of deployments
11. Total Deployments Trend: This compares the deployment count from the previous period to the current period

### Execution Tags <a href="#execution-tags" id="execution-tags"></a>

This view contains the data related to pipeline execution tags. It will contain the tags present in the pipeline at the start of execution.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-23e35eab0b0665dacad97ee8cef3a39b89616b59%2Fusing-cd-custom-dashboards-7.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Execution tag: The execution tag will be displayed as `key:value`. For example, if there are 5 tags in a pipeline, there will be 5 rows having 1 tag (`key:value` pair) in each row.

### Organization Tags <a href="#organization-tags" id="organization-tags"></a>

This view contains the data related to the organization tags. It will contain the organization's real-time tags.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-cb04c0eb606a00398cbff13f39f2b4e2c6c505ad%2Fusing-cd-custom-dashboards-10.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Organization tag: The organization tag. It will be displayed as `key:value`. For example, if there are 5 tags in an organization, there will be 5 rows having 1 tag (`key:value` pair) in each row.

### Organizations <a href="#organizations" id="organizations"></a>

This view contains the data related to organizations.

{% hint style="info" %}
This shows only the organizations that had at least 1 pipeline execution (in any project). It does not display organizations that have no pipeline executions.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-a4cce6949b21bd9168c7236849953216d5646ee9%2Fusing-cd-custom-dashboards-11.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Organization tag: The organization tag, displayed as `key:value`. For example, if there are 5 tags in an organization, there will be 5 rows having 1 tag (`key:value` pair) in each row.

### Pipeline Tags <a href="#pipeline-tags" id="pipeline-tags"></a>

This view contains the data related to pipeline tags. It will contain the pipeline's real-time tags.

{% hint style="info" %}
This shows only the pipelines that had at least 1 pipeline execution. It does not display tags for pipelines that were never executed.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-7cde34d5f521c8009784e450dbf6a347ef7e8b57%2Fusing-cd-custom-dashboards-12.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Pipeline tag: The pipeline tag, displayed as `key:value`. For example, if there are 5 tags in a pipeline, there will be 5 rows having 1 tag (`key:value` pair) in each row.

### Service Tags <a href="#service-tags" id="service-tags"></a>

Displays a list of tags associated with a service.

{% hint style="info" %}
Service Tags only display the tags for the services that were part of pipelines that were successfully executed at least once.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-d3f2675b1fb534be478d6b4262124d25d82d388c%2Fusing-cd-custom-dashboards-23.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Service tag: The service tag is displayed as `key:value`. For example, if there are 5 tags in a service, there will be 5 rows having 1 tag (`key:value` pair) in each row.

### Environment Tags <a href="#environment-tags" id="environment-tags"></a>

Displays a list of tags associated with an environment.

{% hint style="info" %}
Environment Tags only displays the tags for the environments that were part of pipelines that were successfully executed at least once.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-18ece694e68b107dc21a56c0a28f08184e55bfb9%2Fusing-cd-custom-dashboards-26.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Environment tag: The environment tag is displayed as `key:value`. For example, if there are 5 tags in an environment, there will be 5 rows having 1 tag (`key:value` pair) in each row.

### Pipelines <a href="#pipelines" id="pipelines"></a>

This view contains the data related to the pipelines.

{% hint style="info" %}
This shows only pipelines that had at least 1 execution. It does not display pipelines that had no executions.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-440cbd85576a63560f0dcfb54ee17620657a279b%2Fusing-cd-custom-dashboards-13.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Created Time: Creation time of the pipeline
2. Modified Name: Modification time of the pipeline
3. Pipeline Name: Name of the pipeline

### Projects <a href="#projects" id="projects"></a>

This view contains the data related to the projects.

{% hint style="info" %}
This shows only projects with at least 1 pipeline execution. It does not display projects that had no pipeline executions.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-6f2cf161e512db46f63b6b523a26e38315467eae%2Fusing-cd-custom-dashboards-14.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Created Time: Creation time of the project
2. Modified Name: Modification time of the project
3. Project Name: Name of the project

### Reverted Deployments <a href="#reverted-deployments" id="reverted-deployments"></a>

This view contains data on reverted pipeline executions.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-1abd0d553a9977bef25d8174fe41c2d6f5be937c%2Fusing-cd-custom-dashboards-15.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

Filter-only Field:

1. Current Aggregation Period:

List of dimensions:

1. Deployment Duration: Duration of the pipeline execution
2. End Time: End time of the pipeline execution
3. Is Revert Execution (Yes / No): Specifies if the execution got reverted
4. Organization ID: Organization identifier where the pipeline got executed
5. Original Execution ID: Original execution id of the pipeline which got reverted
6. Pipeline Name: Name of the pipeline
7. Project ID: Project identifier where the pipeline got executed
8. Start Time: Start time of the pipeline execution
9. Status: Pipeline status (`RUNNING`/`ABORTED`/`SUCCESS` etc.)
10. Trigger Type: Type of trigger used to execute the pipeline (`MANUAL`/`WEBHOOK` etc.)

List of measures:

1. Failed Deployments: The number of deployments that failed with `FAILED`/`ABORTED` statuses
2. Failure Rate: Failure rate of deployments(Failed Deployments divided by total no. of deployments)
3. Last Deployment: Last deployment time
4. Longest Deployment: Longest deployment time
5. Mean duration: Average pipeline duration
6. Mean duration trend: This compares the mean duration trend from the previous period to the current period
7. Mean Time to Restore: Measures the mean time to restore
8. Median Duration: Median duration of the deployment
9. Success Rate: Success rate of deployments (deployments completed with `SUCCESS` status)
10. Total Deployments: Total no. of deployments
11. Total Deployments Trend: This compares the deployment count from the previous period to the current period

### Runtime Inputs <a href="#runtime-inputs" id="runtime-inputs"></a>

This view contains data related to the runtime inputs provided during pipeline execution. This will contain only the user-provided runtime inputs when a pipeline is executed.

{% hint style="info" %}
This view does not show nested runtime inputs. For example, if a service has a variable as a runtime input, and a pipeline also has the service as a runtime input, Harness does not show the service variable in the list. This view also does not store execution inputs.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-ec9706f6cb4ac25fc3ed58ea80a039420eed1aa7%2Fusing-cd-custom-dashboards-16.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. FQN: FQN of the runtime input
2. Input Key: Key of the runtime input
3. Input Value: Value given to the runtime input

### Services <a href="#services" id="services"></a>

This view contains the data related to the service and environment configurations.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-38bcd83dafc8bdedf2d72c0135cbc1f4e7bbdbb2%2Fusing-cd-custom-dashboards-22.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

Filter-only Field:

1. Current Aggregation Period:

List of dimensions:

1. Artifact Display Name: Display name of the artifact being deployed in the execution
2. Artifact Tag: Artifact tag being deployed
3. Deployment Type: Deployment type of the service
4. Environment Name: Name of the environment being used for the execution
5. Environment Type: Type of the environment(`Production`/`PreProduction`)
6. Rollback Duration: Rollback duration of the stage
7. RolledBack (Yes / No): Signifies if the stage execution rolled back
8. Service Name: Name of the service being deployed.
9. Service Stage End Time: End time of the CD stage
10. Service Stage Start Time: Start time of the CD stage
11. Service Stage Status: Status of the CD stage

List of measures:

1. Failed Service Deployments: The number of deployments that failed with `FAILED`/`ABORTED` statuses
2. Failure Rate: Failure rate of deployments(Failed Deployments divided by total no. of deployments)
3. Service Count: Distinct no. of services that got deployed
4. Success Rate: Success rate of the deployment
5. Successful Service Deployments: The number of executions that completed with `SUCCESS` status.
6. Total Service Deployments: Total no. of deployments

### Users <a href="#users" id="users"></a>

This view contains the data related to users.

{% hint style="info" %}
This shows only the users who have triggered at least 1 pipeline execution. It does not display users who did not trigger any pipeline execution.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-9a9b73e2453b15eb4258bbe3ae9ff9a04a21aabd%2Fusing-cd-custom-dashboards-19.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Created At: Time at which user was created
2. Email ID: Email ID of the user
3. Updated At: Time at which the user was updated
4. User Name: User name

### Deployments and Services V2 <a href="#deployments-and-services-v2" id="deployments-and-services-v2"></a>

This explore can be used to visualize CD data related to pipeline, stage, and step executions. Each explore has a set of views. The views present in this explore are:

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-704db9e7312e6f7322c91020c9fc0547cd34a46b%2Fusing-cd-custom-dashboards-2.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

The following sections describe the fields and usage for each view listed in the preceding image.

### CD Stage Execution Helm Manifest Info <a href="#cd-stage-execution-helm-manifest-info" id="cd-stage-execution-helm-manifest-info"></a>

This view contains data related to the Helm manifest used in CD Stage executions. The data is recorded per CD stage execution, meaning that if there are 10 executions of a single service with a linked Helm manifest, this view will also have 10 records.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-1c5c99bef9d4c0b3afe15d2706e17045c3bd8b1e%2Fusing-cd-custom-dashboards-3.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Chart Version: Chart version of the manifest
2. Helm Version: Helm version of the manifest
3. Manifest ID: Manifest ID configured in the service
4. Manifest Type: Type of the manifest. This dimension stores data only for the manifest type `HelmChart`.

### CD Stage Executions <a href="#cd-stage-executions" id="cd-stage-executions"></a>

This view contains data on CD stage executions. The data is recorded per CD stage execution, meaning if there are 10 pipeline executions that contain a single CD stage, then this view will also have 10 records.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-a3b07a929969ed7b02bdfd00ce6e2937e08fc23c%2Fusing-cd-custom-dashboards-4.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Artifact Display Name: Display name of the artifact being deployed in the execution
2. Deployment Type: Deployment type of the service
3. Environment Full Identifier: Environment identifier being used for the execution
4. Environment Group Name: Name of the environment group being used for the execution
5. Environment Name: Name of the environment being used for the execution
6. Environment Type: Type of the environment(`Production`/`PreProduction`)
7. Execution Strategy Type: The execution strategy used for the execution. This filter applies only to executions that occur after it is added and does not retrieve strategy details for earlier executions.
8. Failure Details: Failure message of the execution(if the CD Stage failed)
9. Infrastructure Name: Name of the infrastructure being used for the execution
10. Rollback Duration: Rollback duration of the stage
11. RolledBack (Yes / No): Signifies if the stage execution rolled back
12. Service Name: Name of the service being deployed.

List of measures:

1. Failed Count: The number of stage executions that failed with `FAILED`/`ABORTED`/`EXPIRED` statuses.
2. Failure Rate: Rate of failure(Failed Count divided by the total no. of stage executions)
3. Service Count: Count of distinct services deployed.
4. Success Rate: Rate of success(Successful Count divided by the total no. of stage executions)
5. Successful Count: The number of stage executions that completed with `SUCCESS`/`SUCCEEDED` statuses.
6. Total Count: Total no. of stage executions

### Custom Stage Executions <a href="#custom-stage-executions" id="custom-stage-executions"></a>

This view contains the data related to the Custom Stage executions. The data is recorded per Custom Stage Execution, meaning that if there are 10 pipeline executions that contain a single Custom stage, this view will also have 10 records.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-3a5be74356bd047a737df38c14506f21858f9792%2Fusing-cd-custom-dashboards-5.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Environment Name: Name of the environment being used for the execution
2. Environment Type: Type of the environment(`Production`/`PreProduction`)
3. Failure Details: Failure message of the execution(if the Custom Stage failed)
4. Infrastructure Name: Name of the infrastructure being used for the execution

### Deployments (V2) <a href="#deployments-v2" id="deployments-v2"></a>

This view contains the data related to the pipeline executions. The data is recorded per pipeline execution, meaning if there are 10 pipeline executions, then this view will also have 10 records.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-bb4c35ca86f6cec9385e1a264efba6bd18584ec7%2Fusing-cd-custom-dashboards-6.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

Filter-only Field:

1. Current Aggregation Period:

List of dimensions:

1. Deployment Duration: Duration of the pipeline execution
2. End Time: End time of the pipeline execution
3. Execution URL: URL of pipeline execution
4. Organization ID: Organization identifier where the pipeline got executed
5. Pipeline Name: Name of the pipeline
6. Project ID: Project identifier where the pipeline got executed
7. Start Time: Start time of the pipeline execution
8. Status: Pipeline status(`RUNNING`/`ABORTED`/`SUCCESS` etc.)
9. Trigger Type: Type of trigger used to execute the pipeline(`MANUAL`/`WEBHOOK` etc.)

List of measures:

1. Change Failure Rate: Total deployments that have been reverted divided by the total no. of deployments
2. Failed Deployments: The number of deployments that failed with `FAILED`/`ABORTED` statuses
3. Failure Rate: Failure rate of deployments(Failed Deployments divided by total no. of deployments)
4. Last Deployment: Last deployment time
5. Longest Deployment: Longest deployment time
6. Mean duration: Average pipeline duration
7. Mean duration trend: This compares the mean duration trend from the previous period to the current period
8. Median Duration: Median duration of the deployment
9. Success Rate: Success rate of deployments(deployments completed with `SUCCESS` status)
10. Total Deployments: Total no. of deployments
11. Total Deployments Trend: This compares the deployment count from the previous period to the current period

### Execution Tags (V2) <a href="#execution-tags-v2" id="execution-tags-v2"></a>

This view contains the data related to the pipeline execution tags. It will contain the tags present in the pipeline at the start of execution.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-23e35eab0b0665dacad97ee8cef3a39b89616b59%2Fusing-cd-custom-dashboards-7.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Execution tag: The execution tag is displayed as `key:value`. For example, if there are 5 tags in a pipeline, there will be 5 rows having 1 tag (`key:value` pair) in each row.

### Service Execution Tags <a href="#service-execution-tags" id="service-execution-tags"></a>

This view contains the data related to the service execution tags. It will contain the tags present in the service at the start of execution.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-d40d0725906aa6e570cf1aef65d7084f10456eb1%2Fusing-cd-custom-dashboards-24.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Service Execution tag: The execution tag is displayed as `key:value`. If there are 5 tags in a service, there will be 5 rows having 1 tag(`key:value` pair) in each row.

### Environment Execution Tags <a href="#environment-execution-tags" id="environment-execution-tags"></a>

This view contains the data related to the environment execution tags. It will contain the tags present in the environment at the start of execution.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-5a8a2354610e561a892289388f2126ccb8e4f17e%2Fusing-cd-custom-dashboards-27.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Environment execution tag: The execution tag is displayed as `key:value`. If there are 5 tags in an environment, there will be 5 rows having 1 tag (`key:value` pair) in each row.

### Harness Approval Step Execution <a href="#harness-approval-step-execution" id="harness-approval-step-execution"></a>

This view contains the data related to the Harness Approval Step Executions. If any field in this view is selected, only data related to executions with a Harness approval step will be shown. For e.g. if there are Jira approval and Harness Approval steps in a single pipeline execution, then selecting fields from this view will only show Harness approval data.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-f399e47fe415cf2b45bb4b3a01e192da5c9f5068%2Fusing-cd-custom-dashboards-8.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Approval Action: Action taken for the approval(`APPROVE`/`REJECT`)
2. Approval Action Time: Time at which approval action was done
3. Comments: Comments added to the approval action
4. Email: Email of the user who took the action
5. Name: Name of the user who took the action

List of measures:

1. Total Approved Steps: Total no. of approved Harness approval steps
2. Total Rejections: Total no. of rejected Harness approval steps

### Jira Step Execution <a href="#jira-step-execution" id="jira-step-execution"></a>

This view contains the data related to the Jira Step Executions. If any field in this view is selected, it will only show data related to executions that have Jira steps (JIRA CREATE/UPDATE/APPROVAL). For example, if there are Jira steps and Harness Approval steps in a single pipeline execution, selecting fields in this view will only show Jira step data.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-15cfeb1ae1c4e236e3444ef2df4b0aa4aeead9ad%2Fusing-cd-custom-dashboards-9.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Issue Type: Jira ticket issue type
2. Jira URL: URL of the Jira ticket
3. Step Type: Step type of the Jira step(`JIRA CREATE`/`JIRA UPDATE`/`JIRA APPROVAL`)
4. Ticket Status: Status of the Jira ticket

List of measures:

1. Total Approved Jira Approval Steps: Total no. of approved Jira approval steps
2. Total Rejections Jira Approval: Total no. of rejected Jira approval steps

### Organization Tags (V2) <a href="#organization-tags-v2" id="organization-tags-v2"></a>

This view contains the data related to the organization tags. It will contain the organization's real-time tags.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-cb04c0eb606a00398cbff13f39f2b4e2c6c505ad%2Fusing-cd-custom-dashboards-10.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Organization tag: The organization tag will be displayed as `key:value`. For example, if there are 5 tags in an organization, there will be 5 rows having 1 tag (`key:value` pair) in each row.

### Organizations (V2) <a href="#organizations-v2" id="organizations-v2"></a>

This view contains the data related to organizations.

{% hint style="info" %}
This shows only the organizations that had at least 1 pipeline execution (in any project). It does not display organizations that had no pipeline execution.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-a4cce6949b21bd9168c7236849953216d5646ee9%2Fusing-cd-custom-dashboards-11.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Organization Name: The name of the organization where the pipeline execution happened.

### Pipeline Tags (V2) <a href="#pipeline-tags-v2" id="pipeline-tags-v2"></a>

This view contains the data related to the pipeline tags. It will contain the pipeline's real-time tags.

{% hint style="info" %}
This shows only the pipelines that had at least 1 pipeline execution. It does not display tags for pipelines that were never executed.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-7cde34d5f521c8009784e450dbf6a347ef7e8b57%2Fusing-cd-custom-dashboards-12.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Pipeline tag: The pipeline tag will be displayed as `key:value`. For example, if there are 5 tags in a pipeline, there will be 5 rows having 1 tag (`key:value` pair) in each row.

To see this dimension in a single column, right-click the dimension or column and select **Unpivot**.

![](https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-a18e2037ae914e53a16036e8b5c61d5c75c433ac%2Fcustom-dashboard-unpivot.png?alt=media)

### Service Tags (V2) <a href="#service-tags-v2" id="service-tags-v2"></a>

Displays a list of tags associated with a service.

{% hint style="info" %}
Service Tags display only tags for services that were part of pipelines successfully executed at least once.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-d3f2675b1fb534be478d6b4262124d25d82d388c%2Fusing-cd-custom-dashboards-23.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Service tag: The service tag is displayed as `key:value`. For example, if there are 5 tags in a service, there will be 5 rows having 1 tag (`key:value` pair) in each row.

### Environment Tags (V2) <a href="#environment-tags-v2" id="environment-tags-v2"></a>

Displays a list of tags associated with an environment.

{% hint style="info" %}
Environment Tags only displays the tags for the environments that were part of pipelines that were successfully executed at least once.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-18ece694e68b107dc21a56c0a28f08184e55bfb9%2Fusing-cd-custom-dashboards-26.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Environment tag: The environment tag is displayed as `key:value`. For example, if there are 5 tags in an environment, there will be 5 rows having 1 tag (`key:value` pair) in each row.

### Pipelines (V2) <a href="#pipelines-v2" id="pipelines-v2"></a>

This view contains the data related to the pipelines.

{% hint style="info" %}
This shows only the pipelines that had at least 1 execution. It does not display pipelines that had no execution.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-440cbd85576a63560f0dcfb54ee17620657a279b%2Fusing-cd-custom-dashboards-13.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Created Time: Creation time of the pipeline
2. Modified Name: Modification time of the pipeline
3. Pipeline Name: Name of the pipeline

### Services (V2) <a href="#services-v2" id="services-v2"></a>

This view contains the data related to the service.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-f4ee7a772029593db622b6c1fc24515346cd16d3%2Fusing-cd-custom-dashboards-25.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Created Time: Creation time of the service
2. Modified Name: Modification time of the service
3. Service Name: Name of the Service
4. Store Type: Indicates whether the service is INLINE OR REMOTE.

### Environments <a href="#environments" id="environments"></a>

This view contains the data related to the environment.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-2b6886594fc725dab1ecebaf94ff8515f73ab70f%2Fusing-cd-custom-dashboards-28.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Created Time: Creation time of the environment
2. Modified Name: Modification time of the environment
3. Environment Name: Name of the environment
4. Store Type: Indicates whether the environment is INLINE OR REMOTE.

### Projects (V2) <a href="#projects-v2" id="projects-v2"></a>

This view contains the data related to the projects.

{% hint style="info" %}
This shows only the projects that had at least 1 pipeline execution. It does not display projects that had no pipeline execution.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-6f2cf161e512db46f63b6b523a26e38315467eae%2Fusing-cd-custom-dashboards-14.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Created Time: Creation time of the project
2. Modified Name: Modification time of the project
3. Project Name: Name of the project

### Reverted Deployments (V2) <a href="#reverted-deployments-v2" id="reverted-deployments-v2"></a>

This view contains data on pipeline executions that have been reverted.

{% hint style="info" %}
This only works for deployments reverted using the post-production rollback feature. This requires the pipeline YAML to have a `reverted_execution_id` tag. Go to [Use reverted executions to capture the mean time to restore](/continuous-delivery/use-continuous-delivery/monitor-deployments/dora-metrics-dashboard.md#use-reverted-executions-to-capture-mean-time-to-restore) to configure this.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-1abd0d553a9977bef25d8174fe41c2d6f5be937c%2Fusing-cd-custom-dashboards-15.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

Filter-only Field:

1. Current Aggregation Period:

List of dimensions:

1. Deployment Duration: Duration of the pipeline execution
2. End Time: End time of the pipeline execution
3. Is Revert Execution (Yes / No): Specifies if the execution got reverted
4. Organization ID: Organization identifier where the pipeline got executed
5. Original Execution ID: Original execution ID of the pipeline that got reverted
6. Pipeline Name: Name of the pipeline
7. Project ID: Project identifier where the pipeline got executed
8. Start Time: Start time of the pipeline execution
9. Status: Pipeline status(`RUNNING`/`ABORTED`/`SUCCESS` etc.)
10. Trigger Type: Type of trigger used to execute the pipeline(`MANUAL`/`WEBHOOK` etc.)

List of measures:

1. Failed Deployments: The number of deployments that failed with `FAILED`/`ABORTED` statuses
2. Failure Rate: Failure rate of deployments(Failed Deployments divided by total no. of deployments)
3. Last Deployment: Last deployment time
4. Longest Deployment: Longest deployment time
5. Mean duration: Average pipeline duration
6. Mean duration trend: This compares the mean duration trend from the previous period to the current period
7. Mean Time to Restore: Measures the mean time to restore
8. Median Duration: Median duration of the deployment
9. Success Rate: Success rate of deployments(deployments completed with `SUCCESS` status)
10. Total Deployments: Total no. of deployments
11. Total Deployments Trend: This compares the deployment count from the previous period to the current period

### Runtime Inputs (V2) <a href="#runtime-inputs-v2" id="runtime-inputs-v2"></a>

This view contains data related to the runtime inputs provided during pipeline execution. This will contain only the user-provided runtime inputs when a pipeline is executed.

{% hint style="info" %}
This view does not show nested runtime inputs. For example, if a service has a variable as a runtime input, and a pipeline also has the service as a runtime input, Harness does not show the service variable in the list. This view also does not store execution inputs.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-ec9706f6cb4ac25fc3ed58ea80a039420eed1aa7%2Fusing-cd-custom-dashboards-16.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. FQN: FQN of the runtime input
2. Input Key: Key of the runtime input
3. Input Value: Value given to the runtime input

### Stage Executions (Approvals/CD/Custom) <a href="#stage-executions-approvalscdcustom" id="stage-executions-approvalscdcustom"></a>

This view contains the data related to the stage executions. It shows data for Approvals/CD and Custom stages.

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-dc17d883121e6ea5323d173811b831de8d804596%2Fusing-cd-custom-dashboards-17.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

{% hint style="info" %}
**AUTOMATIC FILTERING**

* When you select CD-specific fields (for example, from **CD Stage Execution Helm Manifest Info**, **CD Stage Executions**, **Environments**, or **Services** views), the data displayed will only include CD stage–related executions.\
  This means that the **Stage Executions (Approvals/CD/Custom)** view will not contain data for Custom or Approval stages.
* Similarly, when you select fields from the **Custom Stage Executions** view, only custom stage data is displayed.
* Using fields from **Harness Approval Step Execution** automatically filters the data to stages that contain a Harness approval step.
* Using fields from **Jira Step Execution** automatically filters the data to stages that contain Jira steps (Create, Update, Approval).
  {% endhint %}

Filter-only Field:

1. Current Aggregation Period:

List of dimensions:

1. End Time: End time of the stage execution
2. Stage Name: Name of the stage
3. Stage Status: Current status of the stage(`RUNNING`/`FAILED` etc.)
4. Stage Type: Type of the stage(`Approvals`/`CD`/`Custom`)
5. Start Time: Start time of the stage execution

List of measures:

1. Stage Execution Duration: Average stage execution duration

### Step Executions (Jira Create/Jira Update/All Approval Steps) <a href="#step-executions-jira-createjira-updateall-approval-steps" id="step-executions-jira-createjira-updateall-approval-steps"></a>

This view contains the data related to the step executions. It shows data only for these steps:

* Jira Create
* Jira Update
* Jira Approval
* Custom Approval
* ServiceNow Approval
* Harness Approval

  <figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-f58b54d0c518abdc8775d8d49b8b8964d1d7de35%2Fusing-cd-custom-dashboards-18.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

Filter-only Field:

1. Current Aggregation Period:

List of dimensions:

1. End Time: End time of the step execution
2. Failure Details: Failure message of the step(if it failed)
3. Start Time: Start time of the step execution
4. Step Name: Name of the step
5. Step Status: Current status of the step(`RUNNING`/`FAILED` etc.)
6. Step Type: Type of the step

List of measures:

1. Failed Count: The number of step executions that failed with `FAILED`/`ABORTED`/`EXPIRED` statuses.
2. Step Execution Duration: Average step execution duration
3. Successful Count: The number of step executions that completed with `SUCCESS`/`SUCCEEDED` statuses.

### Users (V2) <a href="#users-v2" id="users-v2"></a>

This view contains the data related to the users.

{% hint style="info" %}
This shows only the users who have triggered at least 1 pipeline execution. It does not display users who did not trigger any pipeline execution.
{% endhint %}

<figure><img src="https://3694223630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1JhZ4oKIppwY7d5AhPj%2Fuploads%2Fgit-blob-9a9b73e2453b15eb4258bbe3ae9ff9a04a21aabd%2Fusing-cd-custom-dashboards-19.png?alt=media" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

List of dimensions:

1. Created At: Time at which user was created
2. Email ID: Email ID of the user
3. Updated At: Time at which the user was updated
4. User Name: User name

### Troubleshooting <a href="#troubleshooting" id="troubleshooting"></a>

This section covers common questions and issues you may encounter when working with custom dashboards for CD deployments.

<details>

<summary>Understanding drill-down behavior</summary>

When you click a deployment metric in a dashboard widget (for example, clicking a bar in a "Deployment Frequency" chart), a drill-down page opens showing detailed pipeline execution data.

**How drill-down works:**

The drill-down displays data at the **stage level**, not the pipeline level. Each row in the drill-down represents a **unique combination** of:

* Pipeline execution
* Service name
* Environment name
* Start time
* End time
* Other stage-specific attributes

**Key point**: If a pipeline has multiple CD stages (for example, 2 stages deploying to different environments), the drill-down shows **multiple rows for that single pipeline execution**, one row per stage.

**Example**:

* A pipeline executes once with 2 stages (Deploy to QA, Deploy to Prod)
* The widget shows: **1 deployment**
* The drill-down shows: **2 rows** (one for each stage)

This is expected behavior because the drill-down provides stage-level details, including service, environment, and timing information for each deployment stage.

</details>

<details>

<summary>Dashboard count mismatch between widget and drill-down</summary>

**Issue**: The count displayed in a dashboard widget (for example, "Total Deployments - Prod: 10") does not match the number of rows shown in the drill-down view (for example, 20 rows).

**Cause**: This is expected behavior, not a bug. As explained above:

* **Widget count**: Shows the number of pipeline executions (counts each pipeline once)
* **Drill-down rows**: Shows stage-level details where each row represents a stage execution

**Example**:

* A pipeline with 2 CD stages executes 10 times
* Widget shows: **10 deployments**
* Drill-down shows: **20 rows** (10 pipelines × 2 stages)

The drill-down provides stage-level visibility, showing exactly which services were deployed to which environments for each pipeline execution.

</details>

<details>

<summary>Dashboard not showing recent data</summary>

**Issue**: Dashboard widgets stop displaying data after a certain date, even though pipelines continue to execute successfully.

**Possible causes**:

1. **Data synchronization issue**: The Change Data Capture (CDC) service that synchronizes execution data to the dashboards may have experienced an interruption.
2. **Dashboard configuration**: The dashboard may include date filters or time-range settings that exclude recent data.

**Troubleshooting steps**:

1. **Check your dashboard filters**:
   * Review the time range filter on your dashboard
   * Ensure date filters are set to include recent data
   * Check if any custom filters are excluding recent executions
2. **Verify pipeline executions**:
   * Confirm that pipelines are executing successfully in the Harness UI
   * Check the execution history to ensure data is being generated
3. **Test with a new widget**:
   * Create a new widget using the same explore (for example, "Deployments and Services V2")
   * If the new widget shows current data, the issue may be with the specific widget configuration
   * Consider recreating affected widgets
4. **Contact Harness Support**:
   * If the issue persists across multiple dashboards and widgets, there may be a data synchronization issue
   * Provide the dashboard URL and the date range when data stopped appearing
   * Include information about which explores are affected

{% hint style="info" %}
Dashboard data is populated through a Change Data Capture (CDC) service. In rare cases, this service may require intervention from Harness Support to restore data flow.
{% endhint %}

</details>

{% @harness-feedback/feedback %}