Track non-default config values in telemetry?

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Telemetry Data
    • None
    • 2
    • None

      Does it make sense for us to track e.g. every mongosh startup where config settings differ from the defaults, and which settings specifically differ? This might seem like a good way to fine-tune the defaults we provide, by looking at what users intentionally modify.

              Assignee:
              Unassigned
              Reporter:
              Anna Henningsen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: