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

Add mloginfo --queries support for aggregation queries #338

Closed
jonrangel opened this issue Feb 12, 2015 · 2 comments
Closed

Add mloginfo --queries support for aggregation queries #338

jonrangel opened this issue Feb 12, 2015 · 2 comments

Comments

@jonrangel
Copy link

Add support for cataloging distinct aggregation pipelines 'shapes' and aggregating count/min/max/avg runtime, just as for find() and update() operations.

@thechrisproject
Copy link

This would be great! I found while digging through some recent logs that our aggregate queries were the highest total time and had great variability. Having visibility via mloginfo would be fantastic.

@stennie stennie added this to the 1.6.0 milestone Sep 4, 2019
@stennie stennie self-assigned this Sep 4, 2019
@stennie stennie removed their assignment Dec 23, 2019
@stennie stennie removed this from the 1.6.0 milestone Dec 23, 2019
@stennie
Copy link
Collaborator

stennie commented Dec 23, 2019

Aggregation commands log a pipeline rather than a query pattern, so it isn't obvious how to create concise output that would be analogous to find or update queries with specific critieria. Pipelines can also be rewritten as a result of server Pipeline Optimization.

However, mloginfo --queries does output stats for aggregate queries (count, min, max, etc) without trying to infer a pattern.

To investigate aggregation issues I'd suggest:

  • use mloginfo --queries to identify potentially problematic aggregate commands
  • use mlogfilter to extract log lines of interest (by namespace, duration, command, ...)
  • use mplotqueries to explore the outliers in your filtered output

After reviewing available log information I'm going to close this as not viable for now, but please feel free to comment if you have suggestions on how to extract a meaningful summary.

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

4 participants