Profiler filters
It would be nice to be able to filter the content of the profiler in the Atlas GUI.
The profiler has proved to be very useful and maybe it could be even better.
Currently you can only filter by "Top namespace operations"; and it would be nice to also filter by:
- readConcern: this is because the ones hitting a secondary node are usually not a concern to me. They tend to be ad hoc queries which do not always have a supporting index and that is ok.
- Also, when Operation = command, it could actually be many things. It might be a simple FIND or an AGGREGATE or even an INSERT. So filtering by the type of Operation would be good.
Carlos
shared this idea
-
Daniel
commented
It would be nice to be able to filter the content of the profiler in the Atlas GUI.
The profiler has proved to be very useful and maybe it could be even better.Currently you can only filter by "Top namespace operations"; and it would be nice to also filter by:
readConcern: this is because the ones hitting a secondary node are usually not a concern to me. They tend to be ad hoc queries which do not always have a supporting index and that is ok.
Also, when Operation = command, it could actually be many things. It might be a simple FIND or an AGGREGATE or even an INSERT. So filtering by the type of Operation would be good. -
Carlos
commented
It would be nice to be able to filter the content of the profiler in the Atlas GUI.
The profiler has proved to be very useful and maybe it could be even better.Currently you can only filter by "Top namespace operations"; and it would be nice to also filter by:
- readConcern: this is because the ones hitting a secondary node are usually not a concern to me. They tend to be ad hoc queries which do not always have a supporting index and that is ok.
- Also, when Operation = command, it could actually be many things. It might be a simple FIND or an AGGREGATE or even an INSERT. So filtering by the type of Operation would be good.
Thanks