-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
rabbitmq plugin: make deprecated heathcheck optional #7823
Comments
If it's deprecated, maybe we should just stop collecting this? |
pabigot
added a commit
to pabigot/telegraf
that referenced
this issue
Jul 29, 2020
pabigot
added a commit
to pabigot/telegraf
that referenced
this issue
Jul 29, 2020
I think #7920 handles this: manual run with |
ssoroka
pushed a commit
that referenced
this issue
Aug 10, 2020
Looks like this is already resolved as of #7920 |
idohalevi
pushed a commit
to idohalevi/telegraf
that referenced
this issue
Sep 29, 2020
arstercz
pushed a commit
to arstercz/telegraf
that referenced
this issue
Mar 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The latest RabbitMQ servers issue a diagnostic each time the HTTP management API is used to invoke a node health check from the rabbitmq telegraf plugin. This makes the rabbitmq server logs very noisy.
Relevant telegraf.conf:
System info:
Telegraf 1.14.5 monitoring rabbitmq 3.8.5 using the rabbitmq:3-management docker image
Steps to reproduce:
Enable
inputs.rabbitmq
with RabbitMQ 3.8.5 and monitor the logsExpected behavior:
No complaints in the rabbitmq logs due to use of the rabbitmq monitoring plugin.
Actual behavior:
Messages like:
appear at the telegraf check rate of 0.1 Hz.
Additional info:
See: rabbitmq/rabbitmq-cli#426
The text was updated successfully, but these errors were encountered: