You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @zdyj3170101136 ,
I'm not sure I'm following: the doc you linked to describes our Trace Retention policies (that is, how long a trace is retained in the Datadog platform, once it has already been ingested/"sampled").
Our standard retention period for traces in the Datadog platform is 15 days.
Please clarify your question if I have not already answered it above. Thanks!
Generally speaking, the client will retain a trace until all spans in the trace have completed. Once all spans in the trace have completed, the client pushes the trace onto the buffer to be written out to the agent. The client flushes traces to the agent at an interval of 2s.
I'm not sure what "p99 policy" you're referring to; the only p99 calculation relating to traces that I can think of is the DDSketch metrics for span duration, which is not computed in the tracer.
In Datadog's trace tail sampling strategy (https://docs.datadoghq.com/tracing/trace_pipeline/trace_retention/), whether to sample depends on whether the trace has p99 latency, etc.
I assume that this may be implemented by saving each trace in memory by traceid, and then judging after a period of time.
How long will the trace be retained in memory?
The text was updated successfully, but these errors were encountered: