Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set default log level in tests to debug #1513

Merged
merged 6 commits into from
Feb 12, 2024
Merged

Conversation

Stringy
Copy link
Collaborator

@Stringy Stringy commented Jan 23, 2024

Description

During test containerization, the default log level was erroneously set to INFO. This switches it back to debug.

@Stringy Stringy requested a review from a team as a code owner January 23, 2024 10:09
@Stringy Stringy force-pushed the giles/debug-logging-in-tests branch 4 times, most recently from abb1994 to 7e532b1 Compare January 24, 2024 15:29
@Stringy Stringy force-pushed the giles/debug-logging-in-tests branch from ad3c2e9 to 605cb4c Compare February 6, 2024 13:07
@ovalenti
Copy link
Contributor

@Stringy, this is probably part of the goal, but just to make sure : the size of the produced logs for core_bpf is very large. Do we have the right level applied here ?

@Stringy
Copy link
Collaborator Author

Stringy commented Feb 12, 2024

Yes, I think it's unavoidable currently. The majority of logs that come from core-bpf are Falco's own debug logging in the modern bpf engine. We could perhaps change them to TRACE in a follow up (?)

@ovalenti
Copy link
Contributor

It is fine, I merely wanted to make sure that the size had been noticed and was expected 👍

Copy link
Contributor

@ovalenti ovalenti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will certainly make it easier to get to the root cause of issues when they happen.

@Stringy Stringy merged commit 003a523 into master Feb 12, 2024
54 checks passed
@Stringy Stringy deleted the giles/debug-logging-in-tests branch February 12, 2024 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants