-
Notifications
You must be signed in to change notification settings - Fork 1
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
Complete nm-vllm-production-monitoring chart #11
Conversation
…lm-charts into add-grafana-configuration
- name: grafana | ||
repository: https://grafana.github.io/helm-charts | ||
version: 7.3.9 | ||
- name: nm-vllm | ||
repository: https://helm.neuralmagic.com | ||
version: 0.1.1 | ||
version: 0.1.2 | ||
- name: nm-vllm-grafana-dashboards | ||
version: 1.0.0 | ||
repository: https://helm.neuralmagic.com | ||
- name: prometheus | ||
repository: https://prometheus-community.github.io/helm-charts | ||
version: 25.12.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to confirm, we didn't intend to make the grafana and prometheus charts conditionally configurable via the enabled flag here did we? I know we talked about it but it seemed like maybe that was something that could be done in the future
charts/nm-vllm-production-monitoring/templates/config-map-datasources.yaml
Show resolved
Hide resolved
evaluation_interval: 30s | ||
scrape_interval: 10s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
During exploration, it turned out having values like these was important to getting the dashboard to work right
No description provided.