search

deadtrickster / prometheus_rabbitmq_exporter

Prometheus.io exporter as a RabbitMQ Managment Plugin plugin
MIT License
290 stars 72 forks source link

rabbitmq_exporter not listening through plugin on rabbitmq 3.7.8 #59

Open DrHashi opened 5 years ago

DrHashi commented 5 years ago

Even though the plugin is enabled, the node itself is not listening for requests on 9419 or collecting.

root@ip-10-2-249-45:~# curl localhost:9419/metrics curl: (7) Failed to connect to localhost port 9419: Connection refused

root@ip-10-2-249-45:~# rabbitmq-plugins enable prometheus_rabbitmq_exporter The following plugins have been configured: prometheus_rabbitmq_exporter rabbitmq_management rabbitmq_management_agent rabbitmq_peer_discovery_aws rabbitmq_peer_discovery_common rabbitmq_web_dispatch Applying plugin configuration to rabbit@ip-10-2-249-45.us-east-2.compute.internal... Plugin configuration unchanged.

root@ip-10-2-249-45:~# [E] prometheus_rabbitmq_exporter 3.7.2.3 [ ] rabbitmq_amqp1_0 3.7.8 [0/906] [ ] rabbitmq_auth_backend_cache 3.7.8 [ ] rabbitmq_auth_backend_http 3.7.8 [ ] rabbitmq_auth_backend_ldap 3.7.8 [ ] rabbitmq_auth_mechanism_ssl 3.7.8 [ ] rabbitmq_consistent_hash_exchange 3.7.8 [ ] rabbitmq_event_exchange 3.7.8 [ ] rabbitmq_federation 3.7.8 [ ] rabbitmq_federation_management 3.7.8 [ ] rabbitmq_jms_topic_exchange 3.7.8 [E] rabbitmq_management 3.7.8 [e] rabbitmq_management_agent 3.7.8 [ ] rabbitmq_mqtt 3.7.8 [E] rabbitmq_peer_discovery_aws 3.7.8 [e] rabbitmq_peer_discovery_common 3.7.8 [ ] rabbitmq_peer_discovery_consul 3.7.8 [ ] rabbitmq_peer_discovery_etcd 3.7.8 [ ] rabbitmq_peer_discovery_k8s 3.7.8 [ ] rabbitmq_random_exchange 3.7.8 [ ] rabbitmq_recent_history_exchange 3.7.8 [ ] rabbitmq_sharding 3.7.8 [ ] rabbitmq_shovel 3.7.8 [ ] rabbitmq_shovel_management 3.7.8 [ ] rabbitmq_stomp 3.7.8 [ ] rabbitmq_top 3.7.8 [ ] rabbitmq_tracing 3.7.8 [ ] rabbitmq_trust_store 3.7.8 [e] rabbitmq_web_dispatch 3.7.8 [ ] rabbitmq_web_mqtt 3.7.8 [ ] rabbitmq_web_mqtt_examples 3.7.8 [ ] rabbitmq_web_stomp 3.7.8 [ ] rabbitmq_web_stomp_examples 3.7.8`

root@ip-10-2-249-45:~# netstat -tulnp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:25672 0.0.0.0: LISTEN 2685/beam.smp tcp 0 0 0.0.0.0:4369 0.0.0.0: LISTEN 2787/epmd tcp 0 0 0.0.0.0:22 0.0.0.0: LISTEN 1171/sshd tcp 0 0 0.0.0.0:15672 0.0.0.0: LISTEN 2685/beam.smp tcp6 0 0 :::5672 ::: LISTEN 2685/beam.smp tcp6 0 0 :::9100 ::: LISTEN 1145/node_exporter tcp6 0 0 :::4369 ::: LISTEN 2787/epmd tcp6 0 0 :::22 ::: LISTEN 1171/sshd udp 0 0 0.0.0.0:68 0.0.0.0: 945/dhclient udp 0 0 0.0.0.0:46175 0.0.0.0: 2685/beam.smp ]

[ root@ip-10-2-249-45:~# systemctl status rabbitmq-server.service rabbitmq-server.service - RabbitMQ broker Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2018-10-22 10:03:41 EDT; 7min ago Process: 2573 ExecStop=/usr/lib/rabbitmq/bin/rabbitmqctl shutdown (code=exited, status=0/SUCCESS) Main PID: 2685 (beam.smp) Status: "Initialized" Tasks: 85 Memory: 81.8M CPU: 10.667s CGroup: /system.slice/rabbitmq-server.service ├─2685 /usr/lib/erlang/erts-10.1.1/bin/beam.smp -W w -A 64 -MBas ageffcbf -MHas ageffcbf -MBlmbcs 512 -MHlmbcs 512 -MMmcs 30 -P 1048576 -t 5000000 -stbt db -zdbbl 128000 -K true -- -root /usr/l ├─2787 /usr/lib/erlang/erts-10.1.1/bin/epmd -daemon ├─2929 erl_child_setup 32768 ├─2970 inet_gethost 4 └─2971 inet_gethost 4

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. ]

deadtrickster commented 5 years ago

Hi where this port 9419 comes from? btw path is /api/metrics by default

DrHashi commented 5 years ago

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

deadtrickster commented 5 years ago

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

DrHashi commented 5 years ago

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?

deadtrickster commented 5 years ago

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.