-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
Monitoring based on prometheus #2042
Comments
Hi @Owners! I'm ready to prepare PR with 2 roles:
We use this configuration in our company.
I'm happy to help this project now and use metrics out of the box later, without local patches. |
@bobahspb nice! big thanks! |
@bobahspb If you can use helm, I would strongly prefer it. We want to keep Kubespray code as simple as possible and not duplicate efforts other teams are using. Now that ansible has a native helm module, it should be quite easy to get prometheus-operator deployed. I had some good luck on my own actually. |
@arslanbekov , yes, it works with RBAC. I can send you our current version directly. @mattymo , thanks for fast answer. Metrics collector is as popular subsystem as logs. EFK is included. What is different between metrics and logs? |
@bobahspb Any news on this? |
if anyone needs this role (prometheus), we can put it in Ansible Galaxy repo |
I could try it out :) We have a big dev cluster testing on. And we're currently looking into how to best monitor with ease. So please :) |
I'll try to do this week |
Looks like it was fixed by #2547 |
Should it declares some ingress so that it is automatically exposed through host-based route? |
@desaintmartin I think it is better to have such a function, or implement it by using Node port or externalIP. |
FEATURE REQUEST
It would be very convenient if monitoring was automatically raised monitoring cluster based on prometheus-operator.
As an example: https://itnext.io/kubernetes-monitoring-with-prometheus-in-15-minutes-8e54d1de2e13
The text was updated successfully, but these errors were encountered: