Skip to content
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

[RFE] Enable Puma Control Server #19826

Open
dmetzger57 opened this issue Feb 10, 2020 · 2 comments
Open

[RFE] Enable Puma Control Server #19826

dmetzger57 opened this issue Feb 10, 2020 · 2 comments

Comments

@dmetzger57
Copy link
Contributor

It would be great to pull more useful metrics off the CloudForms puma environment. This can be done using sensu if the puma control server is available.

https://github.com/puma/puma/tree/a3136985887d44c79e623b1408a41779b71d8b23#controlstatus-server

Stats and GC Stats are available: https://github.com/puma/puma/blob/master/lib/puma/app/status.rb

We are using Sensu to monitor our CloudForms deployment ~250 appliances today.
I wanted to pull more information off the Puma servers themselves to get details such as Ruby GC performance etc.

I am pulling items such as the MIQ Queue size as well as DB connections total, active, waiting.

We were going to deploy the Sensu Puma plugin which pulls all the metrics and stores into Graphite/InfluxDB: https://github.com/sensu-plugins/sensu-plugins-puma.

There is also a metrics plugin for Apache: https://github.com/sensu-plugins/sensu-plugins-apache that uses mod_status.

Adding both the puma socket and mod_status would provide any standards-complient tool such as sensu/collectd/etc to pull data from the appliance.

It would also support using this data internally to have this type of dashboard ultimately be part of the product.

@dmetzger57
Copy link
Contributor Author

@miq-bot miq-bot added the stale label Jun 11, 2020
@miq-bot
Copy link
Member

miq-bot commented Jun 11, 2020

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants