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

Add Configuration for Monitoring via Prometheus Operator #49

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

josephschadlick
Copy link

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.

failureThreshold: 1
initialDelaySeconds: 10
periodSeconds: 10
ports:
- containerPort: {{ .Values.metrics.port }}
name: metrics
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
name: metrics
name: http-metrics

ports:
- containerPort: {{ .Values.metrics.port }}
name: metrics
protocol: TCP
Copy link
Member

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.

Suggested change
protocol: TCP

@uhthomas
Copy link
Member

Is there any reason to use a service monitor rather than a pod monitor?

@josephschadlick
Copy link
Author

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.

@josephschadlick josephschadlick changed the title Add ServiceMonitor and associated Service resource configuration Add Configuration for Monitoring via Prometheus Operator Aug 22, 2023
@lucasfcnunes
Copy link

I do prefer the service approach because of scaling and routing.
I noticed that #57 did the "same thing" you did before moving from ServiceMonitor to PodMonitor.

@maxpain
Copy link

maxpain commented Oct 13, 2024

Please add also Grafana Dashboard ConfigMap

@maxpain
Copy link

maxpain commented Oct 13, 2024

any updates on this PR?

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

Successfully merging this pull request may close these issues.

4 participants