rhobs / rhobs/observability-operator

Can I monitor serviceMonitors of both apiVersions (monitoring.rhobs/v1 and monitoring.coreos.com/v1) with a MonitoringStack

Open
#970 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
51
Forks
90
Avg merge
5d 15h
Merged PRs (30d)
22

Description

Dear maintainers,

I have not found any hint in the documentation and I could not get this working, so:

Can I monitor both the "old" serviceMonitors as well as the "new" ones using the cluster observability operator?

We have a whole heap of helm charts that already provide a serviceMonitor in apiVersion: monitoring.coreos.com/v1?, while the COO documentation only mentions serviceMonitors with apiVersion: monitoring.rhobs/v1`.

It would save us and our developers a lot of time if we would not have to change the apiVersion in every serviceMonitor (or even worse, make it configurable as the "new" one might not work in other clusters).

Thanks a lot in advance!

Kind Regards,
Johannes

"old" apiVersion
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
new apiVersion
apiVersion: monitoring.rhobs/v1
kind: ServiceMonitor

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names MonitoringStack and ServiceMonitor resources but no repository files, tests, or entry points. Start by locating the code that selects ServiceMonitors for a MonitoringStack and compare support for monitoring.rhobs/v1 and monitoring.coreos.com/v1. Done means establishing whether both API versions can be monitored, with tests or documentation reflecting the result.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.