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
{{ message }}
This repository has been archived by the owner on Mar 6, 2023. It is now read-only.
If I remember correctly (I might not!), the sampling rate in dapper was encoded as an "integer reciprocal"... i.e., 1024 for 1/1024 sampling. Some sort of fixed-point fraction would also work, I guess.
Reporting out-of-band: it's kind of a long story, but the short version is that it made things easier on the analysis size and it seemed like a small price to pay. (Certain statistical statements could be made locally rather than after trace assembly)
@bensigelman mentioned in a comment the idea of making
(Context).Sampled
an int32.This would allow detailed sampling information to be stored, such as the sampling rate, whether the trace was forced sampled, etc.
The text was updated successfully, but these errors were encountered: