@ -292,11 +292,26 @@ during normal operation beyond that of Consul's available metrics.
See the below [table](#additional-integration-checks-performed) for an outline of the features added by the official integration.
See the below [table](#additional-integration-checks-performed) for an outline of the features added by the official integration.
<Note>
Currently, the annotations configured by the Helm overrides with Consul RPC TLS enabled
assume server and ca certificate secrets are shared with the Datadog agent release namespace and mount the valid <code>tls.crt</code>, <code>tls.key</code>,
and <code>ca.crt</code> secret volumes at the <code>/etc/datadog-agent/conf.d/consul.d/certs</code> path on the Datadog Agent, agent container.
</Note>
### Helm Chart Configuration
### Helm Chart Configuration
<CodeBlockConfig heading={"Datadog Consul Checks"}>
<Tabs>
<CodeBlockConfig heading={"Datadog Consul Checks"}>
Consul Helm Chart Overrides
```yaml
```yaml
global:
tls:
enabled: true
enableAutoEncrypt: true
acls:
manageSystemACLs: true
metrics:
metrics:
enabled: true
enabled: true
enableAgentMetrics: true
enableAgentMetrics: true
@ -305,7 +320,34 @@ See the below [table](#additional-integration-checks-performed) for an outline o
@ -342,6 +384,12 @@ This method implements the collection via Openmetrics as that is fully supported
to scrape the agent's metrics API endpoint using either RPC TLS and Consul ACLs as necessary.
to scrape the agent's metrics API endpoint using either RPC TLS and Consul ACLs as necessary.
</Note>
</Note>
<Note>
Currently, the annotations configured by the Helm overrides with Consul RPC TLS enabled
assume server and ca certificate secrets are shared with the Datadog agent release namespace and mount the valid <code>tls.crt</code>, <code>tls.key</code>,
and <code>ca.crt</code> secret volumes at the <code>/etc/datadog-agent/conf.d/consul.d/certs</code> path on the Datadog Agent, agent container.