Ctrlk
Sign UpGet a DemoContact Us
For the complete documentation index, see llms.txt. This page is also available as Markdown.

What's supported in Harness SRM

Health and change sources supported by Harness SRM.

This topic lists health sources and change sources supported by Harness Service Reliability Management (SRM).

All SRM features supported in Harness SaaS are also supported in the Self-Managed Enterprise Edition.

Go to Harness SRM overview to understand SRM features and functionality. Go to Harness SRM key concepts to understand SRM concepts.

Go to SRM release notes to review released features. Go to SRM early access features to review early access features.

Go to Supported platforms and technologies to understand supported technologies for other Harness modules.

Health sources

Health sources in Harness SRM are APM (Application Performance Monitoring) or log providers that allow you to monitor changes in your service's health trends.

Harness SRM supports the following health sources:

  • AppDynamics

  • CloudWatch

  • Datadog

  • Dynatrace

  • Elasticsearch

  • Google Cloud Operations (formerly Stackdriver)

  • Loki

  • New Relic

  • Prometheus

  • Splunk Log

  • Splunk Observability (formerly SignalFX)

  • Sumologic

  • Custom health source

Go to Health sources to add a health source.

Harness offers support for all major APM vendors, but there are cases where a customized APM is needed. The Custom Health Source lets you customize APMs of your choice.

Change sources

Change sources enable you to monitor change events related to deployments, infrastructure changes, and incidents.

Harness SRM supports the following change sources:

  • Harness Continuous Delivery

  • Harness Chaos Engineering

  • Harness Feature Flag

  • PagerDuty

  • Custom change source

Go to Change sources to add a change source.

Governance

Harness Policy As Code uses Open Policy Agent (OPA) as the central service to store and enforce policies for the different entities and processes across the Harness platform.

You can centrally define and store policies and then select where (which entities) and when (which events) they will be applied.

You can define and store policies directly in the OPA service in Harness.

You will be able to use remote Git or other repositories, such as OCI-compatible registries, to define and store policies used in Harness.

Go to these pages to configure Harness Policy As Code:

FEEDBACK_BUTTON

PreviousOverview
NextGet Started

Last updated

Was this helpful?