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

question: should a otlp gateway option be included in chart? #1173

Open
chap-dr opened this issue Jan 27, 2025 · 0 comments
Open

question: should a otlp gateway option be included in chart? #1173

chap-dr opened this issue Jan 27, 2025 · 0 comments

Comments

@chap-dr
Copy link

chap-dr commented Jan 27, 2025

Hi.

I am looking into adopting the k8s-monitoring v2 chart as it seem to fit quite nicely as a drop in replacement for our prometheus operator setup. (we have loki, tempo and mimir configured locally)

This is a very well made chart the values file is well documented and validations are really great, however I seem to be hitting a bit of a wall when it comes to shipping opentelemetry things using the otel gateway part of the chart. (which may very well be due to my lack of understanding of opentelemetry in general) to me it seems like this chart is missing an option for setting up a gateway? it just assumes that I have one at hand? Is that deliberate or something that is missing? In case I want to somehow have the chart also set one up, what would be the recommended approach to that? Or perhaps I'm looking at this the entirely different way and I can make due with the "traditional" metric and log shipping options? but would that not result in me missing some labels to correlate metrics, logs and traces?

I hope this question is ok to ask here. 🤞 🙏

@chap-dr chap-dr changed the title question: otlp gateway option included in chart? question: should a otlp gateway option be included in chart? Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant