-
Notifications
You must be signed in to change notification settings - Fork 411
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
collector Connection reset #3117
Comments
It's HTTP exporter It's gRPC port @bongmu could you please share the instrumentation CR? |
opentelemetry-collector.yaml apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
name: demo
namespace: opentelemetry-operator-system
spec:
config: |
receivers:
otlp:
protocols:
grpc:
endpoint: 0.0.0.0:4317
http:
endpoint: 0.0.0.0:4318
processors:
memory_limiter:
check_interval: 1s
limit_percentage: 75
spike_limit_percentage: 15
batch:
send_batch_size: 10000
timeout: 10s
exporters:
logging:
zipkin:
endpoint: "http://zipkin-server.zipkin:9411/api/v2/spans"
format: proto
service:
pipelines:
traces:
receivers: [otlp]
processors: [memory_limiter, batch]
exporters: [logging,zipkin]
metrics:
receivers: [otlp]
processors: [memory_limiter, batch]
exporters: [logging]
logs:
receivers: [otlp]
processors: [memory_limiter, batch]
exporters: [logging] opentelemetry-instrumentation.yaml: apiVersion: opentelemetry.io/v1alpha1
kind: Instrumentation
metadata:
name: instrumentation
namespace: opentelemetry-operator-system
spec:
exporter:
endpoint: http://demo-collector.opentelemetry-operator-system:4317
propagators:
- tracecontext
- baggage
- b3
sampler:
type: parentbased_traceidratio
argument: "0.25"
python:
env:
- name: OTEL_EXPORTER_OTLP_ENDPOINT
value: http://demo-collector:4318
java:
image: ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-java:latest
env:
- name: OTEL_EXPORTER_OTLP_ENDPOINT
value: http://demo-collector.majorbio-erp-dev:4317
dotnet:
env:
- name: OTEL_EXPORTER_OTLP_ENDPOINT
value: http://demo-collector.opentelemetry-operator-system:4318 |
It instructs java agent to report data to |
Oops, I was careless, deleting this doesn't seem to work, although my app Instrumentation, OpenTelemetryCollector, is in the majorbio-erp-dev namespace |
I pasted it wrong. My apps are all in the opentelemetry-operator-system namespace, but it still reports that error. |
Component(s)
No response
Describe the issue you're reporting
This all seems to be working fine, I don’t understand why my app is resetting the Connection?:
K8S YAML: ... annotations: instrumentation.opentelemetry.io/inject-java: opentelemetry-operator-system/instrumentation [otel.javaagent 2024-07-09 15:38:41:967 +0800] [OkHttp http://demo-collector.opentelemetry-operator-system:4317/...] ERROR io.opentelemetry.exporter.internal.http.HttpExporter - Failed to export spans. The request could not be executed. Full error message: Connection reset
The text was updated successfully, but these errors were encountered: