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

[SURE-4340] Prometheus Metrics missing #1408

Closed
8 tasks done
ulikl opened this issue Mar 15, 2023 · 3 comments
Closed
8 tasks done

[SURE-4340] Prometheus Metrics missing #1408

ulikl opened this issue Mar 15, 2023 · 3 comments

Comments

@ulikl
Copy link

ulikl commented Mar 15, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I would like to monitor the fleet functionality via Prometheus metrics.
I found this was already implemented and merge via PR "Add Prometheus metrics to Fleet #769" at May 13, 2022.

The fleet controller has no prometheus metrics code included in release 0.5.1 (released Jan 23) and master branch.

But the code is no longer there. Just the modules are still in go.mod and go.sum.
What happend to this feature?

Expected Behavior

I would expect metrics at the controller endpoint /metrics on port 6060

Steps To Reproduce

No response

Environment

- Architecture: amd64
- Fleet Version: 0.5.1

Issues

@kkaempf
Copy link
Collaborator

kkaempf commented Apr 4, 2023

See SURE-4340

@davidstauffer davidstauffer added the JIRA Must shout label May 11, 2023
@davidstauffer davidstauffer changed the title Prometheus Metrics missing [SURE-4340] Prometheus Metrics missing May 11, 2023
@manno
Copy link
Member

manno commented May 26, 2023

#769 was superseded by #770. That was partially reviewed and closed.

At first glance I see a few problems with #770, which make this complex:

  • exposing port 6060 of the fleet-controller for /metrics also allows access to /debug/pprof, which is insecure. We probably want to enable pprof only with --debug.
  • as mentioned in the previous review we want to enable metrics only with --enable-metrics.
  • adding .global to the bundledeployment, to store the cluster name from rancher is a smart workaround, but I think we should modify fleet to store a fleet cluster identifier (=cleaned up labels from the live cluster) in the bundledeployments status instead of bundleDep.Spec.StagedOptions.Helm.Values.Global.Fleet.ClusterLabels[clusterNameLabel]? I'm afraid of side effects with the helm values related code.

@manno manno added this to the 2023-Q4-v2.7x milestone May 26, 2023
@kkaempf kkaempf modified the milestones: v2.8.0, 2024-Q1-2.8x Sep 27, 2023
@manno manno modified the milestones: 2024-Q1-2.8x, v2.9.0 Nov 27, 2023
@manno
Copy link
Member

manno commented Dec 20, 2023

Build this for the new controller-runtime controllers only. This is a requirement for #1850

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

No branches or pull requests

5 participants