pt-query-digest QPS, concurrency and other time-related stats don't work on Percona Server enhanced slow logs

Bug #996649 reported by Jay Janssen
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Triaged
Medium
Unassigned

Bug Description

This seems like a reason not to use the enhanced slow query log with pt-query-digest. The slow log I am looking at has SET timestamp= before each query. Can that be used to get timing information?

If not, can/should a datestamp be added to the enhanced stats so pt-query-digest can get all this info?

Revision history for this message
Jay Janssen (jay-janssen) wrote :

Examples:

# Overall: 796.65k total, 467 unique, 0 QPS, 0x concurrency ______________
# Query 1: 0 QPS, 0x concurrency, ID 0x5826F19FB94468B5 at byte 308614642

the Digest also doesn't show the time range of the queries run.

tags: added: percona-server pt-query-advisor
Changed in percona-toolkit:
status: New → Triaged
Revision history for this message
Rolf (rolf-winmutt) wrote :

This affects mysql community 5.5 and most likely 5.1. This is particularly problematic when trying to play back old slow logs through a review function. In my case I am trying add some enhancements to Box's Anemometer and have to rely on bin logs as the timestamps do work there.

tags: added: slow-log
removed: pt-query-advisor
tags: added: pt-query-digest
Changed in percona-toolkit:
milestone: none → 2.2.5
importance: Undecided → Medium
Changed in percona-toolkit:
milestone: 2.2.5 → none
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-529

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.