Avoid registering queryStats for excessively long collection names

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This came out of the HELP-87160 investigation. It seems that we register queryStats for commands ran against non-existent collections regardless if the attempted collection name is longer than the 255 character limit enforced in `db.createCollection`. This is because the query just returns an empty result but doesn't error.

      This guardrail is an ask from the Customer Observability team.

            Assignee:
            Arun Banala
            Reporter:
            Mariano Shaar
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: