What's supported in 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.
For information about what's supported for other Harness modules and the Harness Platform overall, go to Supported platforms and technologies.
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
To learn how to add a health source, go to Health sources.
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
To learn how to add a change source, go to Change sources.
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.
Currently, you can define and store policies directly in the OPA service in Harness.
Soon, you will be able to use remote Git or other repos (for example, OCI-compatible registries) to define and store the policies used in Harness.