Change Monitoring Quickstart
A Harness Monitored Service is a Service and Environment combination that Harness monitors for:
- Any changes, such as deployments, infrastructure changes (Kubernetes events, auditing, etc), and alerts (PagerDuty, etc)
- Any health trend deviations using logs and metrics obtained from APM/Logging tools
This quickstart walks you through the steps to create a Monitored Service and add a Change Source to track changes.
You'll learn how to:
- Add a Monitored Service to track your service in its environment
- Add a Change Source to track change events
Before You Begin
Harness Monitored Services and Change Sources can be set up without any Harness deployments having been performed, but there won't be much data for Harness to display.
If you already have Harness deployments in this Project, then you can use the Services and Environments from any of those deployments.
If there are no deployments in your Harness account, we recommend that you first follow the steps in a CD Quickstart to perform a deployment: Kubernetes CD Quickstart, Helm CD Quickstart, or Kustomize Quickstart.
Step 1: Add a New Monitored Service
In the Harness Project with the Service you want to monitor, navigate to the Change Intelligence module.
Click Monitored Services.
Click New Monitored Service. The Add New Monitored Service settings appear.
This page displays all the settings that you need to enable to add a service, and to define a Change Source.
Step 2: Add a Service
A Service represents your microservices, Serverless functions, and other workloads logically.
When you add a Service as a Monitored Service, it allows you to associate change records, actions, logs, metrics, and, SLO’s to the respective service.
In Overview under the Service tab, Application is selected by default in the Type field.
In Create or select a Service, choose the Harness Service to be monitored from the list.
In Create or select an Environment, choose Environment where the Harness Service is deployed from the list.
Environments represent your deployment targets logically (QA, Prod, etc). When you add an Environment to a Monitored Service, it allows you to associate change records, actions, logs, metrics, and, SLO’s to the respective service within its associated environment.
The Monitored Service Name field auto-populates the concatenation of the Harness Service and Environment names.
Step 3: Define Your Sources
A Change Source is a combination of a Harness Service and associated Environment that monitors change events related deployments, infrastructure changes, and alerts.
To create a Change Source, click Add New Change Source. The Edit Change Source settings appear.
To define the Change Source, select Deployment in Provider Type under Select Change Source.
Click Harness CD NextGen.
In Source Name, enter a name for the source.
The Monitored Service gets listed as shown below.
The CHANGES (Last 24H) column displays all the changes related to deployments, infrastructure, and alerts. Click the name of the desired Monitored Service in the list, to spot trends or patterns that project into the future.
Now you are ready to track change events like:
- Deployments in Harness CD
- Infrastructure changes such as Kubernetes events, and more
- Alerts from PagerDuty
In this tutorial, you learned how to:
- Add a Monitored Service to Harness
- Add a Change Source which enables change events tracking
See Health Monitoring to setup a Health Source to track Health Trends of your Service.