Skip to content
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

Document / Standardize parsing arbitrary data from queries into fields #31

Open
gtowey opened this issue Jul 3, 2012 · 0 comments
Open

Comments

@gtowey
Copy link
Contributor

gtowey commented Jul 3, 2012

Currently it would be helpful to be able to easily add more custom fields besides the current hostname and size. For instance, you could add a query comment that includes the originating application user, or name of the application feature making the query, then be able to correlate query performance to application-specific categories. This is quite helpful for most end-users.

There are several parts that need to happen:

  1. fields and values need to be parsed from the query in the --filter argument in pt-query-digest
  2. Those columns must be added to the history table as fieldname_max
  3. The unique index on the history table should include those columns.

This should first just be documented, showing people how they can do this for themselves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant