Skip to content

Conversation

@Areson
Copy link
Collaborator

@Areson Areson commented Mar 17, 2025

No description provided.

// If debugging is turned on dump the raw values from performance_schema.events_statements_histogram_global
if blip.Debugging {
blip.Debug("Bucket Number|Bucket Timer Low|Bucket Timer High|Count Bucket|Count Bucket and Lower|Bucket Quantile")
rows, err := c.db.QueryContext(ctx, "SELECT * FROM performance_schema.events_statements_histogram_global")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably best to order by what Blip will actually see/use, then also handle logging timestamps, i.e. the fact that logs will have virtually same ts means they'll order randomly in DD, so we won't be able to see the real order of rows. Maybe emit just 1 big log event to bypass all log ordering (and possibly log filtering)?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that it will get split by newline even if I combine it, though that may fix the ordering issue. I'll test it out and see what happens.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated. Output from a single large string is broken up but the ordering is preserved.

@Areson Areson merged commit e5f4a35 into main Mar 20, 2025
3 checks passed
@Areson Areson deleted the ioberst-debug-latency branch March 20, 2025 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants