-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
[kube-prometheus-stack] Enable otlp receiver #5080
Comments
You could use the
|
@bartvanackooij let me try out, thanks |
Edit: I misunderstood how Prometheus was using OTLP. The OpenTelemetry Demo was a good reference for configuring this correctly. What would be required to also open port prometheus:
prometheusSpec:
additionalArgs:
- name: web.enable-otlp-receiver
value: ""
additionalConfig:
otlp:
promoteResourceAttributes:
- service.instance.id
- service.name
- service.namespace
- cloud.availability_zone
- cloud.region
- container.name
- deployment.environment.name
- k8s.cluster.name
- k8s.container.name
- k8s.cronjob.name
- k8s.daemonset.name
- k8s.deployment.name
- k8s.job.name
- k8s.namespace.name
- k8s.pod.name
- k8s.replicaset.name
- k8s.statefulset.name
translationStrategy: NoUTF8EscapingWithSuffixes
tsdb:
outOfOrderTimeWindow: 30m
service:
additionalPorts:
- name: otlp
port: 4317
targetPort: 4317 |
If followed the instructions here: https://prometheus.io/docs/guides/opentelemetry/#send-opentelemetry-metrics-to-the-prometheus-server I then configured an opentelemetry otel exporter with a similar url: https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/otlphttpexporter/README.md The otel exporter complained about an invalid port because it is not expecting the path in the url. |
Is your feature request related to a problem ?
For new Prometheus 3.0 to receive OTLP metrics, OTLP receiver feature needs to be enabled via cli arg
web.enable-otlp-receiver
. This option is not available at this moment in helmchart.Describe the solution you'd like.
Add option to enable
otlp-receiver
Describe alternatives you've considered.
n/a
Additional context.
No response
The text was updated successfully, but these errors were encountered: