You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And otel.metrics.exporter = none
still spring reporting issue
[otel.javaagent 2023-06-01 04:25:25:656 +0000] [OkHttp http://localhost:4317/...] ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Failed to export metrics. The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:4317
[otel.javaagent 2023-06-01 04:25:25:656 +0000] [OkHttp http://localhost:4317/...] ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Failed to export metrics. The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:4317
Collector version
otel/opentelemetry-collector-contrib:0.77.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
K8s Centos Setup
K8s Windows Setup
Local Windows Setup
[otel.javaagent 2023-06-01 04:25:25:656 +0000] [OkHttp http://localhost:4317/...] ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Failed to export metrics. The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:4317
Additional context
No
The text was updated successfully, but these errors were encountered:
I believe this should be reported in the java repo, as it appears the client is sending metrics even with the configuration off? @open-telemetry/java-approvers @open-telemetry/java-instrumentation-approvers any ideas?
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Component(s)
cmd/otelcontribcol
What happened?
In spring application 3.0.5
using dependency
And
otel.metrics.exporter = none
still spring reporting issue
[otel.javaagent 2023-06-01 04:25:25:656 +0000] [OkHttp http://localhost:4317/...] ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Failed to export metrics. The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:4317
Steps to Reproduce
Added in application properties
spring.application.name=test
otel.exporter.otlp.traces.endpoint=http://localhost:4317
otel.traces.exporter=otlp
otel.metrics.exporter = none
Expected Result
No Error should be reported
Actual Result
[otel.javaagent 2023-06-01 04:25:25:656 +0000] [OkHttp http://localhost:4317/...] ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Failed to export metrics. The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:4317
Collector version
otel/opentelemetry-collector-contrib:0.77.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
K8s Centos Setup
K8s Windows Setup
Local Windows Setup
OpenTelemetry Collector configuration
Log output
[otel.javaagent 2023-06-01 04:25:25:656 +0000] [OkHttp http://localhost:4317/...] ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Failed to export metrics. The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:4317
Additional context
No
The text was updated successfully, but these errors were encountered: