pt-query-digest transaction fingerprints

Registered by Daniel Nichter on 2013-08-02

From bug 1178757: " For my purposes, the low hanging fruit would be simply all the queries concatenated together and run through the standard fingerprinting function for now."

See the bug for more info.

One idea for implementing this: abstract the grouping logic. Make it do "simple" grouping by default, based on a metric value from the log. More complex groupings can implement the same API and affect grouping that way, rather than hard-coding any alternative grouping methods.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.