Skip to content
This repository was archived by the owner on Oct 4, 2021. It is now read-only.

Conversation

@nlopez
Copy link

@nlopez nlopez commented Nov 6, 2018

This adds the prometheus_rabbitmq_exporter RabbitMQ plugin described here to the RabbitMQ image.

This doesn't enable the plugin by default. To do so, AWX cluster operators will need to add prometheus_rabbitmq_exporter to their enabled_plugins config, around here.

I moved launch.sh along with my fetch script for the RabbitMQ modules to a rootfs dir to avoid cluttering the repo root, but I can back this out if you don't want to use this pattern.

@wenottingham
Copy link

Just to state the obvious question: why?

@nlopez
Copy link
Author

nlopez commented Nov 6, 2018

Why include the prom exporter or why the rootfs dir?

Prom exporter: Because I'm running into some queue pileup issues with AWX and want to monitor the AWX RabbitMQ cluster via Prometheus, and figure other AWX users may want to do the same.

@wenottingham
Copy link

Sure, I just wonder whether if we did this we should also have AWX itself throwing metrics into prometheus.

@nlopez
Copy link
Author

nlopez commented Nov 6, 2018

Oh definitely! In fact I'm still hoping to be able to contribute something towards ansible/awx#1963 in the future.

I think this'd still be useful to have at any rate for people wanting to do per component monitoring, similar to how you'd monitor the AWX Postgres DB.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants