Add custom span tags to your spans to customize your observability within Datadog. The span tags are applied to your incoming traces, allowing you to correlate observed behavior with code-level information such as merchant tier, checkout amount, or user ID.
C++ tracing uses “common tags”. These tags can be sourced from both Datadog specific tags or OpenTracing tags, and included via the below:
#include <opentracing/ext/tags.h>
#include <datadog/tags.h>
Note that the Datadog tags are necessary for unified service tagging.
Add tags directly to a span object by calling Span::SetTag. For example:
auto tracer = ...
auto span = tracer->StartSpan("operation_name");
span->SetTag("key must be string", "Values are variable types");
span->SetTag("key must be string", 1234);
Values are of variable type and can be complex objects. Values are serialized as JSON, with the exception of a string value being serialized bare (without extra quotation marks).
To set tags across all your spans, set the DD_TAGS environment variable as a list of key:value pairs separated by commas.
To customize an error associated with one of your spans, use the below:
span->SetTag(opentracing::ext::error, true);
Error metadata may be set as additional tags on the same span as well.
To manually instrument your code, install the tracer as in the setup examples, and then use the tracer object to create spans.
{
// Create a root span.
auto root_span = tracer->StartSpan("operation_name");
// Create a child span.
auto child_span = tracer->StartSpan(
"operation_name",
{opentracing::ChildOf(&root_span->context())});
// Spans can be finished at a specific time ...
child_span->Finish();
} // ... or when they are destructed (root_span finishes here).
Distributed tracing can be accomplished by using the Inject and Extract methods on the tracer, which accept generic Reader and Writer types. Priority sampling (enabled by default) should be on to ensure uniform delivery of spans.
// Allows writing propagation headers to a simple map<string, string>.
// Copied from https://github.com/opentracing/opentracing-cpp/blob/master/mocktracer/test/propagation_test.cpp
struct HTTPHeadersCarrier : HTTPHeadersReader, HTTPHeadersWriter {
HTTPHeadersCarrier(std::unordered_map<std::string, std::string>& text_map_)
: text_map(text_map_) {}
expected<void> Set(string_view key, string_view value) const override {
text_map[key] = value;
return {};
}
expected<void> ForeachKey(
std::function<expected<void>(string_view key, string_view value)> f)
const override {
for (const auto& key_value : text_map) {
auto result = f(key_value.first, key_value.second);
if (!result) return result;
}
return {};
}
std::unordered_map<std::string, std::string>& text_map;
};
void example() {
auto tracer = ...
std::unordered_map<std::string, std::string> headers;
HTTPHeadersCarrier carrier(headers);
auto span = tracer->StartSpan("operation_name");
tracer->Inject(span->context(), carrier);
// `headers` now populated with the headers needed to propagate the span.
}
There are additional configurations possible for both the tracing client and Datadog Agent for context propagation with B3 Headers, as well as to exclude specific Resources from sending traces to Datadog in the event these traces are not wanted to count in metrics calculated, such as Health Checks.
Datadog APM tracer supports B3 headers extraction and injection for distributed tracing.
Distributed headers injection and extraction is controlled by configuring injection/extraction styles. Currently two styles are supported:
DatadogB3Injection styles can be configured using:
DD_PROPAGATION_STYLE_INJECT="Datadog B3"The value of the environment variable is a comma (or space) separated list of header styles that are enabled for injection. By default only Datadog injection style is enabled.
Extraction styles can be configured using:
DD_PROPAGATION_STYLE_EXTRACT="Datadog B3"The value of the environment variable is a comma (or space) separated list of header styles that are enabled for extraction. By default only Datadog extraction style is enabled.
If multiple extraction styles are enabled extraction attempt is done on the order those styles are configured and first successful extracted value is used.
Traces can be excluded based on their resource name, to remove synthetic traffic such as health checks from reporting traces to Datadog. This and other security and fine-tuning configurations can be found on the Security page.
