You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have access to RabbitMQ from 3rd party and I guess not full. It's important to monitor queues to which I have access, but when I connect telegraf to the cluster I'm getting Wrong answer from rabbitmq. Probably auth issue error which is problematic because we monitor any error with it.
acc.AddError(fmt.Errorf("Wrong answer from rabbitmq. Probably auth issue"))
return
}
As you can see from my snippet of JSON file from api/overview I don't have in it Listeners so conditional is true and the plugin writes in my output the error. I think it's an unnecessary condition for Listeners or maybe you can add an option in the plugin configuration for skipping it.
Hi @Levarix. It doesn't look like Listeners is always returned so it seems reasonable that it shouldn't generate an error.
@askainet You wrote this code a few years ago. What do you think about us removing || overview.Listeners == nil from line 411? Is it really an error condition?
I think it's fine to just remove the Listeners condition from that check. If some implementations don't report listeners, this shouldn't be an error, and the count will be reported as 0.
Thanks for the fast answer. When can I expect a fix? I need the information to decide if work on a workaround or can wait for new version @reimda@askainet
I have access to RabbitMQ from 3rd party and I guess not full. It's important to monitor queues to which I have access, but when I connect telegraf to the cluster I'm getting
Wrong answer from rabbitmq. Probably auth issue
error which is problematic because we monitor any error with it.Condition:
telegraf/plugins/inputs/rabbitmq/rabbitmq.go
Lines 411 to 414 in 8eec159
As you can see from my snippet of JSON file from api/overview I don't have in it Listeners so conditional is true and the plugin writes in my output the error. I think it's an unnecessary condition for Listeners or maybe you can add an option in the plugin configuration for skipping it.
The text was updated successfully, but these errors were encountered: