You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
fields and values need to be parsed from the query in the --filter argument in pt-query-digest
Those columns must be added to the history table as fieldname_max
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.
The text was updated successfully, but these errors were encountered:
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:
This should first just be documented, showing people how they can do this for themselves.
The text was updated successfully, but these errors were encountered: