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

Create a ServiceMonitor for the operator metrics endpoint #3370

Closed
iblancasa opened this issue Oct 18, 2024 · 1 comment · Fixed by #3371
Closed

Create a ServiceMonitor for the operator metrics endpoint #3370

iblancasa opened this issue Oct 18, 2024 · 1 comment · Fixed by #3371
Assignees
Labels
enhancement New feature or request needs triage

Comments

@iblancasa
Copy link
Contributor

Component(s)

No response

Is your feature request related to a problem? Please describe.

Currently, we are creating the ServiceMonitor for the OpenTelemetry Operator's metrics endpoint statically from a manifest file. However, this approach has a significant limitation: users may install the operator in a namespace other than the default namespace provided in the manifest. When users specify tlsConfig, this leads to a failure in scraping metrics, as the serverName field in the ServiceMonitor depends on the namespace where the operator was deployed.

Describe the solution you'd like

Enhance the operator to create the ServiceMonitor programmatically, ensuring it is configured automatically based on the namespace where the operator is installed. This will dynamically adjust the serverName and ensure metrics scraping works regardless of the installation namespace.

Describe alternatives you've considered

No response

Additional context

No response

@pavolloffay
Copy link
Member

Cross-linking this with operator-sdk issue to handle SM by OLM operator-framework/operator-sdk#6846

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants