-
Notifications
You must be signed in to change notification settings - Fork 246
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
Panic with multiple OTLP exporters for a single opentelemetry batch processor #2448
Comments
Found a workaround (fanning out before the batch processor and having two batch processors): otelcol.receiver.otlp "default" {
grpc {
endpoint = "0.0.0.0:4317"
}
http {
endpoint = "0.0.0.0:4318"
}
output {
metrics = [otelcol.processor.batch.default.input, otelcol.processor.batch.pov.input]
logs = [otelcol.processor.batch.default.input, otelcol.processor.batch.pov.input]
traces = [otelcol.processor.batch.default.input, otelcol.processor.batch.pov.input]
}
}
otelcol.processor.batch "default" {
output {
metrics = [otelcol.exporter.prometheus.default.input]
logs = [otelcol.exporter.otlphttp.default.input]
traces = [otelcol.exporter.otlphttp.default.input]
}
}
otelcol.processor.batch "pov" {
output {
metrics = [otelcol.exporter.prometheus.default.input]
logs = [otelcol.exporter.otlphttp.grafana_cloud_pov.input]
traces = [otelcol.exporter.otlphttp.grafana_cloud_pov.input]
}
}
// Exporters:
otelcol.auth.basic "default" {
username = sys.env("ALLOY_OTLP_USERNAME")
password = sys.env("ALLOY_API_KEY")
}
otelcol.exporter.otlphttp "default" {
client {
endpoint = sys.env("ALLOY_OTLP_ENDPOINT")
auth = otelcol.auth.basic.default.handler
}
}
otelcol.auth.basic "grafana_cloud_pov" {
username = sys.env("ALLOY_OTLP_USERNAME2")
password = sys.env("ALLOY_API_KEY2")
}
otelcol.exporter.otlphttp "grafana_cloud_pov" {
client {
endpoint = sys.env("ALLOY_OTLP_ENDPOINT2")
auth = otelcol.auth.basic.grafana_cloud_pov.handler
}
} |
Hi, thanks for opening a ticket. I have not been able to reproduce the bug so far. I ran the exact same config on v1.5.1 but I don't get any panic.
|
I think I've hit a similar panic before: grafana/agent#6746 but we'd solved it. It looks like the offending line in |
What's wrong?
I just restarted Alloy with a new config that has multiple OTLP exporters and got a nil-pointer panic. I've attached the logs below.
Steps to reproduce
Start using the config below.
System information
No response
Software version
v1.5.1
Configuration
Logs
The text was updated successfully, but these errors were encountered: