David Goffredo

@DS-Serafin I'm closing this PR as I'm no longer a maintainer of Datadog software and there are now newer alternatives that are supported (dd-trace-cpp, nginx-datadog). Please direct any further questions...

There is the CPU/memory/IO cost of sending traces to the local datadog agent, and separately there is the internet bandwidth cost of the agent sending traces to datadog. Setting `sample_rate`...

The integration test failures are caused by this change, but it's a bit subtle why. I'm playing with it in https://github.com/DataDog/dd-opentracing-cpp/pull/250.

It looks like you're using the dd-opentracing-cpp OpenTracing plugin with Kong. The crash seems to be due to memory corruption. The `std::function` object that is invoked for each HTTP header...

This doesn't look too difficult. It might be covered by telemetry work that we've discussed doing (but haven't scheduled) to collect information like this, kubernetes service, executable name, etc. I'll...

We haven't looked at this, sorry. The telemetry work that I mentioned has stalled, too. It probably won't be a while until I or @cgilmour have the bandwidth to look...

Our experimental Windows support is 64 bit only. I haven't attempted a Windows build yet, so I don't know how we might support 32 bit Windows systems. Our readme says...

The work done in https://github.com/DataDog/dd-opentracing-cpp/commit/9b9248f869fdfb8afc236499138d06a552451113 is not about `X-Datadog-Sampling-Priority` exactly. Instead, it's about keeping track of the "sampling mechanism" associated with the sampling decision. The behavior of extracting `X-Datadog-Sampling-Priority` from...

Yes, there are a few ways that you could do this. If you want to set the probability that any trace is ingested, you can specify the `"sample_rate"` property in...

> My problem with manual keep is I need manual keep : 1 on conditional if a header is present and meets pre determined value. > [...] > I guess...