Something that might be worth entertaining for these scenarios is to use the logging-output configuration article.
You can direct logging to syslog instead of Mongo by using the config:
"logging-output=syslog"
On 2.9 this is behind a feature flag, so you will also need to configure:
"features=[logging-output]"
The flag won't be required for 3.0.
Just be aware that depending on the specific environment, using this feature can cause a lot of logging via the serial console. It caused issues on one particularly large controller.
Something that might be worth entertaining for these scenarios is to use the logging-output configuration article.
You can direct logging to syslog instead of Mongo by using the config: output= syslog"
"logging-
On 2.9 this is behind a feature flag, so you will also need to configure: [logging- output] "
"features=
The flag won't be required for 3.0.
Just be aware that depending on the specific environment, using this feature can cause a lot of logging via the serial console. It caused issues on one particularly large controller.