datadog.proto
Package: solo.io.envoy.config.trace.v3
Types:
Source File: github.com/solo-io/gloo/projects/gloo/api/external/envoy/config/trace/v3/datadog.proto
DatadogRemoteConfig
Configuration for the Remote Configuration feature.
"pollingInterval": .google.protobuf.Duration
"disabled": .google.protobuf.BoolValue| Field | Type | Description |
|---|---|---|
pollingInterval |
.google.protobuf.Duration | Frequency at which new configuration updates are queried. If no value is provided, the default value is delegated to the Datadog tracing library. |
disabled |
.google.protobuf.BoolValue | Disabled remote config. This field does not exist in envoy’s config but allow us to preserve the default behavior when upgrading to envoy v1.31. |
DatadogConfig
Configuration for the Datadog tracer. [#extension: envoy.tracers.datadog]
"collectorUpstreamRef": .core.solo.io.ResourceRef
"clusterName": string
"serviceName": .google.protobuf.StringValue
"collectorHostname": string
"remoteConfig": .solo.io.envoy.config.trace.v3.DatadogRemoteConfig| Field | Type | Description |
|---|---|---|
collectorUpstreamRef |
.core.solo.io.ResourceRef | The upstream to use for submitting traces to the Datadog agent. Only one of collectorUpstreamRef or clusterName can be set. |
clusterName |
string |
The name of the cluster to use for submitting traces to the Datadog agent. Note that the cluster must be defined in the Bootstrap static cluster resources. Only one of clusterName or collectorUpstreamRef can be set. |
serviceName |
.google.protobuf.StringValue | The name used for the service when traces are generated by envoy. |
collectorHostname |
string |
Optional hostname to use when sending spans to the collector_cluster. Useful for collectors that require a specific hostname. Defaults to collector_cluster above. |
remoteConfig |
.solo.io.envoy.config.trace.v3.DatadogRemoteConfig | Configures remote configuration. Remote Configuration allows to configure the tracer from Datadog’s user interface. This feature can drastically increase the number of connections to the Datadog Agent. Each tracer regularly polls for configuration updates, and the number of tracers is the product of the number of listeners and worker threads. |