[BUG] - TraceMempool (and perhaps others?) config setting is ignored

[weebl2000]

Internal/External
External

Area
Other cardano-node tracing config

Summary
It seems TraceMempool configuration is ignored in cardano-node 1.34.0

Steps to reproduce

1. Upgrade to 1.34.0
2. Set TraceMepool to false in config

Expected behavior
I do not see mempool trace logging

System info (please complete the following information):
Ubuntu 20.04 x64, cardano-node 1.34.0 built from source

Additional context
I see a lot of changes regarding tracing. Should we configure this differently? Anyway, this seems to be a regression for 1.34.0 vs 1.33.0 at least.

[weebl2000]

https://github.com/input-output-hk/cardano-node/blob/master/configuration/cardano/mainnet-config-new-tracing.yaml relevant? Should we list this is in the changelog maybe? Seems like a heavy change if everyone needs to edit config to alter tracing.

[rdlrt]

The release notes (or QA process - maybe it does not include testing comparison of EKG metrics against previous version given configuration for hydra builds) are a bit rushed.

The new tracing infra is summarised with a reference to a PR in changelogs, the hydra config templates referred in release notes are not updated either🙁

[weebl2000]

The release notes (or QA process - maybe it does not include testing comparison of EKG metrics against previous version given configuration for hydra builds) are a bit rushed.

The new tracing infra is summarised with a reference to a PR in changelogs, the hydra config templates referred in release notes are not updated eitherslightly_frowning_face

Quite a steep learning curve to understand how to configure tracing again. :( I'll try to figure out how to disable most of the trace logging which is pretty useless for day-to-day operation.

[weebl2000]

This should be fixed by #3668

[Jimbo4350]

Resolved in #3668