We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the Feature Request The Lacework DaemonSet lacework container has the LaceworkLogStdout environment variable set to yes.
yes
Can we make the logging level customizable? At the moment, I look at those logs, they don't seem, very useful to me.
Is your feature request related to a problem? Please describe
Lacework is responsible for 99.x% of the logs in my Namespace, which uses about ~x gb (too many gb) of disk sise in an Elasticsearch cluster.
Describe Preferred Solution We should have the ability to chose a logging level.
The text was updated successfully, but these errors were encountered:
Hey @JPLachance thanks for the feature request. We've opened a ticket internally to implement this feature. We'll aim to add this to our next sprint.
Sorry, something went wrong.
👋🏼 Any progress?
Hi @JPLachance I'm sorry this has fallen off the team's radar. I will raise this again with the team.
For internal reference: https://lacework.atlassian.net/browse/GROW-1119
dmurray-lacework
No branches or pull requests
Feature Request
Describe the Feature Request
The Lacework DaemonSet lacework container has the LaceworkLogStdout environment variable set to
yes
.Can we make the logging level customizable? At the moment, I look at those logs, they don't seem, very useful to me.
Is your feature request related to a problem? Please describe
Lacework is responsible for 99.x% of the logs in my Namespace, which uses about ~x gb (too many gb) of disk sise in an Elasticsearch cluster.
Describe Preferred Solution
We should have the ability to chose a logging level.
The text was updated successfully, but these errors were encountered: