You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Adding label to discover service monitor for prometheus. #97
Hi. I deployed livekit using eks and configured monitoring.
But there was an issue between Prometheus and service monitor. Prometheus can not find the service monitor.
Prometheus check a label which is 'release=prometheus' in the service monitor.
But livekit-server helm chart doesn't make this label.
Please check this helpers code in livekit-helm repository.
I edited service monitor and added the line with release=prometheus and then Prometheus can find the service monitor.
Can I make the PR which add line 'release=prometheus' in service monitor labels if prometheus_port is specified in values.yml?
Hi @Q00, opened a PR (#160) that adds the serviceMonitor.labels field you proposed. The implementation matches what you described in your original issue, with the addition that it works on any custom labels (not just release=prometheus), so operators using non-default Prometheus serviceMonitorSelector configurations can still discover the ServiceMonitor. Tests cover the kube-prometheus-stack case explicitly. Thanks for the clear writeup of the problem.
Activity
hocmemini commentedon Apr 28, 2026
Hi @Q00, opened a PR (#160) that adds the serviceMonitor.labels field you proposed. The implementation matches what you described in your original issue, with the addition that it works on any custom labels (not just release=prometheus), so operators using non-default Prometheus serviceMonitorSelector configurations can still discover the ServiceMonitor. Tests cover the kube-prometheus-stack case explicitly. Thanks for the clear writeup of the problem.