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
Hi,
Great product! I've been using using the Percona Operator for MySQL based on Percona XtraDB Cluster in combination with PMM, this is my configuration.
pmm: enabled: true serverHost: monitoring-service
This is all running great, the only thing I'm noticing, the pmm-client container is generarting a lot of (info), logs. For example:
pmm-client
info
time="2024-03-12T06:55:00.052+00:00" level=info msg="Sending 48 buckets." agentID=/agent_id/xxx component=agent-builtin type=qan_mysql_perf schema_agent
It should be great if there a way we can change the loglevel, for example with:
pmm: enabled: true serverHost: monitoring-service log: level: error
The text was updated successfully, but these errors were encountered:
same could apply to pbm-agent as per documentation here: https://docs.percona.com/percona-backup-mongodb/manage/logpath.html?h=pbm+agent+fl#output-pbm-agent-logs-to-a-file
pbm-agent
Sorry, something went wrong.
No branches or pull requests
Hi,
Great product! I've been using using the Percona Operator for MySQL based on Percona XtraDB Cluster in combination with PMM, this is my configuration.
This is all running great, the only thing I'm noticing, the
pmm-client
container is generarting a lot of (info
), logs.For example:
It should be great if there a way we can change the loglevel, for example with:
The text was updated successfully, but these errors were encountered: