Add Verification Providers

Connect Harness to your verification providers to have Harness verify the success of your deployments. Harness will use your tools to verify deployments and use its machine learning features to identify sources of failures.

To connect a verification provider, do the following:

  1. Click Setup.
  2. Click Connectors.
  3. Click Verification Providers.
  4. Click Add Verification Provider, and select the name of your provider. The Add Verification Provider dialog for your provider appears.

See the provider options below.

Jenkins

The Add Jenkins Verification Provider dialog has the following fields.

Field

Description

Jenkins URL

Enter the URL of Jenkins server.

Authentication Mechanism

Enter the credentials to authenticate with the server.
If you select Username/Password, enter the Jenkins API token or password in the Password field. If you select Token, enter the OpenShift OAuth Access Token in Token. For more information, see Authentication from OpenShift.

Display Name

Enter a display name for the provider. If you are going to use multiple providers of the same type, ensure you give each provider a different name.

Usage Scope

If you want to restrict the use of a provider to specific applications and environments, do the following:

In Usage Scope, click the drop-down under Applications, and click the name of the application.

In Environments, click the name of the environment.

If you add Jenkins as a Verification Provider, it is automatically added as an Artifact Server, and is a single account. Changes made to the Jenkins Artifact Server settings, such as username or Display Name, will also apply to the Jenkins Verification Provider settings, and vice versa.

For token-based authentication, go to http://Jenkins-IP-address/jobs/me/configure to check and change your API access token. The token is added as part of the HTTP header.

AppDynamics

For detailed information on adding AppDynamics as a Verification Provider, and using AppDynamics to verify your deployments, see AppDynamics Verification.

New Relic

For detailed information on adding New Relic as a Verification Provider, and using New Relic to verify your deployments, see New Relic Verification.

Dynatrace

For detailed information on adding Dynatrace as a Verification Provider, and using Dynatrace to verify your deployments, see Dynatrace Verification.

Splunk

For detailed information on adding Splunk as a Verification Provider, and using Splunk to verify your deployments, see Splunk Verification.

ELK Elasticsearch

For detailed information on adding Elasticsearch as a Verification Provider, and using Elasticsearch to verify your deployments, see ELK Elasticsearch Verification.

Logz.io

The Add LOGZ Verification Provider dialog has the following fields.

Field

Description

URL

Enter the URL of the server.

Token

Enter the token for authentication. For more information, see Announcing the Logz.io Search API from logz.io.

Display Name

Enter a display name for the provider. If you are going to use multiple providers of the same type, ensure you give each provider a different name.

Usage Scope

If you want to restrict the use of a provider to specific applications and environments, do the following:

In Usage Scope, click the drop-down under Applications, and click the name of the application.

In Environments, click the name of the environment.

The logz.io API is available to their premium account only.

Datadog

For detailed information on adding Datadog as a Verification Provider, and using Datadog to verify your deployments, see Datadog Verification.

Sumo Logic

For detailed information on adding Sumo Logic as a Verification Provider, and using Sumo Logic to verify your deployments, see Sumo Logic Verification.

Prometheus

For detailed information on adding Prometheus as a Verification Provider, and using Prometheus to verify your deployments, see Prometheus Verification.

Bugsnag

For detailed information on adding Bugsnag as a Verification Provider, and using Bugsnag to verify your deployments, see Bugsnag Verification.

Stackdriver

For detailed information on adding Stackdriver as a Verification Provider, and using Stackdriver to verify your deployments, see Stackdriver Verification.

CloudWatch

For detailed information on adding CloudWatch as a Verification Provider, and using CloudWatch to verify your deployments, see CloudWatch Verification.

Custom Metrics and Logs

If your APM or logging tool is now in the list above, see Custom Metrics and Logs Verification.


How did we do?