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

Limit logs used for direct connection log ingestion to be once per hour

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 7.3.3, 8.0.0-rc5, 7.0.11
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • v8.0, v7.3, v7.0
    • CAR Team 2024-05-13

      The logs for errors and warnings around direct shard operations are both unbounded in the number of log messages that can be triggered per hour. When requesting a log ingestion rule for Atlas, it was brought up that this cannot be unbounded in order to get a log ingestion rule approved.

      To abide by these rules, we change the behavior to the following:

      Warnings - once per hour, log the existing message. Otherwise, rely on the user assertion log at debug(1).

      Errors - once per hour, log the existing message. Otherwise, log at debug(2) the same error but with a new log ID.

      This will allow the log ingestion rules to have a log ID that only occurs once per hour, but users can increase verbosity to see more frequent logs.

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: