Disable OpenObserve infra-metrics + move collector overrides to the wrapper layer - #75
Draft
ashish1099 wants to merge 1 commit into
Draft
Disable OpenObserve infra-metrics + move collector overrides to the wrapper layer#75ashish1099 wants to merge 1 commit into
ashish1099 wants to merge 1 commit into
Conversation
ashish1099
force-pushed
the
feat/openobserve-no-metrics
branch
from
July 12, 2026 02:44
1c5a38c to
f54e4a9
Compare
ashish1099
force-pushed
the
feat/openobserve-no-metrics
branch
from
July 12, 2026 02:50
f54e4a9 to
d47b766
Compare
…rapper OpenObserve stores logs, traces and k8s/security events. Infra metrics and alerting stay in kube-prometheus, which already ships node-exporter, kubelet/cAdvisor scraping and kube-state-metrics. Configure the collector from the first-layer wrapper values.yaml instead of the vendored openobserve-collector subchart, using Helm null-coalescing: - agent: drop the hostmetrics and kubeletstats receivers and the metrics pipeline, leaving a logs-only collector - gateway: drop the prometheus scrape and the otlp metrics receiver; narrow the metrics pipeline to the servicegraph connector, which is derived from traces and has no Prometheus equivalent - disable the bundled kube-state-metrics - pin the OTLP exporter to the in-cluster OpenObserve router Restore charts/openobserve-collector to upstream (exporter endpoints and chart version 0.4.4); the subchart tracks upstream and must not carry local changes. Runtime behaviour is unchanged. Bump the openobserve wrapper chart 0.13.5 -> 0.13.6.
ashish1099
force-pushed
the
feat/openobserve-no-metrics
branch
from
July 12, 2026 03:55
3778fed to
d67a452
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Two things, both rooted in one rule:
<app>/charts/is the vendored upstream subchart and must not carry local customization — a re-vendor silently drops it. Customization belongs in the first-layer wrapper (argocd-helm-charts/openobserve/values.yaml).api.openobserve.ai) on the next re-vendor, silently shipping cluster telemetry off-cluster.Changes
1. Wrapper overrides (first layer) —
openobserve/values.yamlhostmetrics+kubeletstatsdropped (duplicated node-exporter / kubelet-cAdvisor).prometheusscrape and theotlpmetrics receiver are dropped (real infra metrics). Theservicegraphconnector is KEPT — it's derived from traces (service map / RED metrics), exists nowhere in Prometheus, and is part of the tracing experience. The metrics pipeline is narrowed toreceivers: [servicegraph]; the traces pipeline is untouched and still feeds the connector.Uses Helm
null-coalescing to delete upstream keys — the convention already used here (e.g.cert-manager.io/issuer: null).2. Subchart restored to pristine upstream (second layer)
Reverts PR #72's edits to
charts/openobserve-collector/: exporter endpoints back tohttps://api.openobserve.ai/api/default/, chart version back to0.4.4. Net runtime behaviour is unchanged — the collector still exports to the in-cluster router; the setting just lives in the layer that persists.Metric coverage is unaffected
/metrics/cadvisorWrapper chart bumped 0.13.5 → 0.13.6.