Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-27212

Allow configuration for "query not recording (too large)"

    • Type: Icon: New Feature New Feature
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.11
    • Component/s: Diagnostics, Logging
    • None
    • Query
    • Fully Compatible

      Following issue https://jira.mongodb.org/browse/SERVER-5605, we're seeing "query not recording (too large)" when running db.currentOp() to try to track down our slow db queries. It's frustrating not to be able to find the exact query. We're heavy users of Mongo aggregations - some not really even that long in my opinion - but we're finding that all are "too large" to be recorded.

      Can a setting be added to override the size that Mongo considers "too large"? We'd use this to make sure most of our queries are recorded using `db.currentOp()` and the slow query log - to help us track down potential issues.

            Assignee:
            backlog-server-query Backlog - Query Team (Inactive)
            Reporter:
            brad@mixmax.com Brad Vogel
            Votes:
            1 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: