Support tracking with different levels of severity

[lbwexler]

In particular, we have fine grained tracking messages that we would like to turn on when specific problems arise, but are considered too noisy. Would be helpful at a particular client with busy dashboard usage, and tracking of individual widget loads

[lbwexler]

Would like to implement this as follows:

• Use config to store the settings.
• Record level overrides by list of categories (use * for all categories)
• Available levels are "debug"/"info"/"warn"

[lbwexler]

Two other options, one simplifying, the other compleixfying:

• We just have "debug" severity always get logged only, and not saved in DB. No need for level configuration.
• We lean in to the configuration, and also allow specifying levels per user (* for all users)

[amcclain]

Great that we got a feature in here. Which way did we end up going, for the record?

[lbwexler]

The `xhActivityTrackingConfig` soft-config can be used to configure this service, including disabling it completely. Use the 'levels' property in this config to set the minimal severity for persisting any particular message. Entries in this list will be of the following form, where the first matching entry for a message will determine the currently active severity to persist: levels: [ [ username: ['*' or comma-delimited list of usernames], category: ['*' or comma-delimited list of categories], severity: 'DEBUG'|'INFO'|'WARN' ], ... ]

…

On Wed, Jan 22, 2025 at 5:44 PM Anselm McClain ***@***.***> wrote: Great that we got a feature in here. Which way did we end up going, for the record? — Reply to this email directly, view it on GitHub <#3906 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AARTL2NOFZ3FCJBFVSICRYD2MANNXAVCNFSM6AAAAABVKJU35WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBYGQZDAMJXGQ> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>