Extend visibility into your Consul Service Mesh instances to monitor health and improve performance.


This extension utilizes Consul's built-in StatsD export capability to collect metrics from non-Kubernetes Consul instances, both self-managed instances and instances that are managed by HCP Consul.
Requires Dynatrace StatsD integration for metric ingestion. See Dynatrace StatsD documentation for details.
No specific version requirements. Note that the HCP Consul users can export client metrics only.
For details on gathering Consul control plane metrics via StatsD, see our blog post: Automatic intelligent observability into your HashiCorp Consul service mesh.
Following setup, you can verify if the integration works as expected by looking for Consul-related metrics using the Dynatrace metric browser. Check for metrics that have the consul prefix.
Find the extension in Dynatrace Hub and add it to your environment.
Activate metric events for alerting.
The extension comes with the two pre-configured metric events for alerting. To activate them:
Explore Dashboards Classic. After activating the extension, select Dashboards Classic in Dynatrace. You should now see a pre-configured dashboard for Consul - Control Plane.
This extension includes dashboards and alerts for the Consul control plane. It supports Dynatrace metric ingestion via StatsD.
For non-Kubernetes Consul servers, metric export must be manually configured.
This extension supports both HCP Consul and self-managed Consul instances.
Consul server metrics are only applicable for the self-managed version of Consul. Dynatrace supports Consul client metrics for both self-managed Consul instances as well as HCP Consul instances.
This extension has been validated for use with HCP Consul.

HCP Consul Verified: The Dynatrace Consul integration has been verified by HashiCorp for both SaaS and managed use.
When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.