Skip to content
This repository was archived by the owner on Oct 23, 2023. It is now read-only.
This repository was archived by the owner on Oct 23, 2023. It is now read-only.

breadcrumbs instrument log.debug() even when the logging level is info #1055

Open
@lucas-sonnabend

Description

@lucas-sonnabend

I noticed in on of our applications that 5% of the CPU time is spend in _record_log_breadcrumb, called from logging.debug, even though our logging level is not that high.

It would be helpful if the instrumentation would respect the logging level, so if the level is INFO then only messages from that level or higher are instrumented.

This is rather annoying because from my understanding debug logging should be allowed to affect performance because it is only used for development. Anything that instruments logging should respect that behaviour

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions