This topic provides a comprehensive list of health sources and change sources supported by Harness Service Reliability Management (SRM). It covers both Harness SaaS and Harness Self-Managed Enterprise Edition (SMP).
- Health sources
- Change 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. The following health sources are supported:
Harness supported health sources
- Custom health source
- Google Cloud Operations
- New Relic
- Splunk Log
- Splunk Observability (formerly SignalFX)
To learn how to add a health source, go to Health sources.
Change sources enable you to monitor change events related to deployments, infrastructure changes, and incidents. Harness SRM supports the following change sources:
Harness supported change sources
- Custom change source
- Harness CD
- Harness CD NextGen
- Harness Chaos Engineering
- Harness Feature Flag
To learn how to add a change source, go to Change sources.
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.
Harness Self-Managed Enterprise Edition (SMP)
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.