Open DrHashi opened 5 years ago
Hi where this port 9419
comes from? btw path is /api/metrics
by default
Hi where this port
9419
comes from? btw path is/api/metrics
by default
From the default allocated ports, /api/metrics got the same result. Was this designed to work with 3.7.8?
https://github.com/prometheus/prometheus/wiki/Default-port-allocations
root@ip-10-2-252-100:~# curl localhost:9419/api/metrics curl: (7) Failed to connect to localhost port 9419: Connection refused
I'm confused with this port tbh, why you think rabbitmq should use it? this plugin injects itself to management http interface and uses the same port
I'm confused with this port tbh, why you think rabbitmq should use it? this plugin injects itself to management http interface and uses the same port
Since the prometheus documentation uses 9419 for rabbitmq_exporter, it would be assumed that the logging of metrics would be at that port as well.
Are you suggesting that metrics port is 80? If not, what should be?
this is not rabbitmq_exporter this is a different project :-). As previously stated this is a plugin for rabbitmq management plugin. So port is the same (by default 15672)
From: DrHashi notifications@github.com Sent: Monday, October 29, 2018 9:10:28 PM To: deadtrickster/prometheus_rabbitmq_exporter Cc: Ilya Khaprov; Comment Subject: Re: [deadtrickster/prometheus_rabbitmq_exporter] rabbitmq_exporter not listening through plugin on rabbitmq 3.7.8 (#59)
I'm confused with this port tbh, why you think rabbitmq should use it? this plugin injects itself to management http interface and uses the same port
Since the prometheus documentation uses 9419 for rabbitmq_exporter, it would be assumed that the logging of metrics would be at that port as well.
Are you suggesting that metrics port is 80? If not, what should be?
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/deadtrickster/prometheus_rabbitmq_exporter/issues/59#issuecomment-434017595, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAKhF53TVizU0VSNeoSimz1BlykSbl6Pks5up0SUgaJpZM4Xzd3U.
Even though the plugin is enabled, the node itself is not listening for requests on 9419 or collecting.
Oct 22 10:03:41 ip-10-2-249-45 rabbitmq-server[2685]: ## ## Oct 22 10:03:41 ip-10-2-249-45 rabbitmq-server[2685]: ## ## RabbitMQ 3.7.8. Copyright (C) 2007-2018 Pivotal Software, Inc. Oct 22 10:03:41 ip-10-2-249-45 rabbitmq-server[2685]: ########## Licensed under the MPL. See http://www.rabbitmq.com/ Oct 22 10:03:41 ip-10-2-249-45 rabbitmq-server[2685]: ###### ## Oct 22 10:03:41 ip-10-2-249-45 rabbitmq-server[2685]: ########## Logs: /var/log/rabbitmq/rabbit@ip-10-2-249-45.us-east-2.compute.internal.log Oct 22 10:03:41 ip-10-2-249-45 rabbitmq-server[2685]: /var/log/rabbitmq/rabbit@ip-10-2-249-45.us-east-2.compute.internal_upgrade.log Oct 22 10:03:41 ip-10-2-249-45 rabbitmq-server[2685]: Starting broker... Oct 22 10:03:41 ip-10-2-249-45 rabbitmq-server[2685]: systemd unit for activation check: "rabbitmq-server.service" Oct 22 10:03:41 ip-10-2-249-45 systemd[1]: Started RabbitMQ broker. Oct 22 10:03:41 ip-10-2-249-45 rabbitmq-server[2685]: completed with 6 plugins. ]