Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Status Submitted
Categories Atlas
Created by Guest
Created on Feb 21, 2025

Force query to appear in MongoDB Logs and bypass slowms and Profiling settings

As of now operations that are above the slowms threshold appear within the MongoDB Logs. This can be altered by changing the slowms value to a lower/higher value, or by changing the Profiling Levels. If customers want to change the Profiling Settings to collect all operations, they would need to change the Profiling Level to 2. However, doing so can lead to Performance Degradation on the underlying Cluster/Instance as increasing to this level has an effect on database performance and disk use. It would be helpful if there was a way so that when an operation is being executed, that we force said operation to appear within the MongoDB Logs regardless of what Profiling/slowms Settings are set on the mongod level, which would work around the need in some instances to enabled level 2 of the Profiler.
  • Attach files