Skip to content

Allow to create ServiceMonitor for monitoring Collectors in a different namespace #3910

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

Open
sinux-l5d opened this issue Apr 15, 2025 · 0 comments
Labels
area:collector Issues for deploying collector enhancement New feature or request

Comments

@sinux-l5d
Copy link

Component(s)

collector

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

Hello,

Due to project standards, we create our ServiceMonitor in the same namespace as our prometheus-operator instance.

For most charts, we have an option to specify a different namespace where to create the ServiceMonitor.

However, the opentelemetry-operator creates a ServiceMonitor for each collector in the same namespace when spec.observability.metrics.enableMetrics is enabled.

Describe the solution you'd like

Ideally, the CRD should allow a spec.observability.metrics.namespace value that specify in which namespace to put the ServiceMonitor.

Describe alternatives you've considered

I'm using the opentelemetry-kube-stack. I could disable the automatic creation of ServiceMonitor, and create one per collector manually in opentelemetry-operator.extraManifests. This would however lead to duplication of configuration and complexify maintenance.

Additional context

No response

@sinux-l5d sinux-l5d added enhancement New feature or request needs triage labels Apr 15, 2025
@pavolloffay pavolloffay added area:collector Issues for deploying collector and removed needs triage labels Apr 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:collector Issues for deploying collector enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants