-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drop bad queue time events #89
Conversation
🔧 Report generated by pr-comment-scanbuild Scan-Build Report
Bug Summary
Reports
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to track the number of dropped events as a counter or we mostly don't care?
Dropping an event isn't too significant except at the trace level - it doesn't change sampling statistics, the events are latency thresholded and tend to occur in batches, so if we drop some during clearing the class map, we'll usually get some just before or after. We can revisit this if we want to change the way buffering works during dumping the recording. |
What does this PR do?:
Queue time events which are committed during a profiler dump may end up with null scheduler and task attributes, if they are committed just as the class map is being cleared, because the lock can't be acquired when looking up the class name. These events aren't very useful so we'll drop them for now.
Motivation:
Additional Notes:
How to test the change?:
For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance
.Unsure? Have a question? Request a review!