Remove or modify `LOGV2_FOR` macros

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      We have a number of macro definitions to make logging with a component other than the default easier (for example, LOGV2_FOR_RECOVERY, LOGV2_FOR_CATALOG_REFRESH, LOGV2_FOR_TRANSACTION, etc). Using these macros rather than LOGV2 directly is that linters will not catch issues in log lines using these. Additionally, they should also not start with LOGV2_ prefix unless they are part of the LOGV2 package.

      Due to their evasion of linting, it might be worthwhile entirely removing these macros. Alternately, we should at least remove the LOGV2 prefix in their names to prevent confusion.

            Assignee:
            Unassigned
            Reporter:
            Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: