Django log levels are ignored by core agent

[sjamaan]

No matter what I did to the Django log levels, I kept getting this message when running Django management tasks:

[2020-04-02T09:36:06][core_agent][INFO] Initializing logger with log level: Info

This is super annoying, because this causes programs in my crontab to start sending out lots of e-mails because previously quiet tasks would now start producing output.

After a lot of trial and error, I figured out that you can set SCOUT_LOG_LEVEL in Django settings to suppress this message.

This really should be fixed so the agent also honors the Django logging settings, or at least documented under the logging section in the Python documentation. It's really non-obvious that this the agent is a separate thing which ignores the Django logging settings.

[adamchainz]

Hi @sjamaan

Sorry about this. The core agent shouldn't ened to restart with every program in your crontab.

The variable to set is SCOUT_CORE_AGENT_LOG_LEVEL - SCOUT_LOG_LEVEL is the deprecated alias (it invites further confusion with Python log levels). See https://docs.scoutapm.com/#python-configuration .

Agree it would be good to have the core agent respect log silencing, or not forward its output to the Django process. I'll chat with the core agent developers and investigate this to see what we can do.

Thanks,

Adam

[adamchainz]

@sjamaan the fix has been released in 2.14.0, please upgrade :)

[sjamaan]

Cool, thanks. We'll upgrade on the next deploy