-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
improve mntr regex to match user specific keys #25851
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Since the code owner has commented positively on the PR I'll remove the needs triage label, and assign to @freyayunfu as a PR has been opened. Please let me know if this is incorrect. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
receiver/zookeeper
What happened?
Description
Seeing below warning messages from
zookeeperreceiver
Steps to Reproduce
Currently, if the line includes uses specific keys, like
zk_max_pkc-supreme-fox_write_per_namespace\t42343
, our regex would not be able to parse it. And would giveunexpected line in response
warning message.Expected Result
If we update the regex into
Then line
zk_max_pkc-supreme-fox_write_per_namespace\t42343
would be successfully split intoSimilar issue handled by the other repo: influxdata/telegraf#7533
Collector version
v0.82.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: