-
Notifications
You must be signed in to change notification settings - Fork 70
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
Add Configuration for Monitoring via Prometheus Operator #49
base: main
Are you sure you want to change the base?
Conversation
failureThreshold: 1 | ||
initialDelaySeconds: 10 | ||
periodSeconds: 10 | ||
ports: | ||
- containerPort: {{ .Values.metrics.port }} | ||
name: metrics |
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.
name: metrics | |
name: http-metrics |
ports: | ||
- containerPort: {{ .Values.metrics.port }} | ||
name: metrics | ||
protocol: TCP |
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.
Redundant, the default is TCP.
protocol: TCP |
Is there any reason to use a service monitor rather than a pod monitor? |
Updated to use a PodMonitor instead. I have no strong opinion on which to use. ServiceMonitors seem more ubiquitous, but there is no need to manage a service for just this use case. |
I do prefer the service approach because of scaling and routing. |
Please add also Grafana Dashboard ConfigMap |
any updates on this PR? |
I noticed that #11 was created and subsequently closed due to a lack of sufficient metrics exposed in cloudflared.
Now that cloudflared supports a more useful set of metrics (described here), I would like to once again propose enabling configuration for metrics collection via a servicemonitor resource in both the cloudflare-tunnel and cloudflare-tunnel-remote charts.