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

otel.metrics.exporter= none still reporting error (otel/opentelemetry-collector-contrib:0.77.0) #22987

Closed
aayushave opened this issue Jun 1, 2023 · 4 comments

Comments

@aayushave
Copy link

Component(s)

cmd/otelcontribcol

What happened?

In spring application 3.0.5
using dependency

<dependency>
	<groupId>io.opentelemetry.contrib</groupId>
	<artifactId>opentelemetry-runtime-attach</artifactId>
	<version>${opentelemetry.runtime.attach.version}</version>
</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

receivers:
      otlp:
        protocols:
          grpc:
            endpoint: :4317
          http: 
            endpoint: :4318
      
    processors:
      batch:
      memory_limiter:
        check_interval: 1s
        limit_mib: 2000
      

    exporters:
      jaeger:
        endpoint: jaeger-svc:14250
        tls:
          insecure: true
      
    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: [batch]
          exporters: [jaeger]

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

@aayushave aayushave added bug Something isn't working needs triage New item requiring triage labels Jun 1, 2023
@codeboten
Copy link
Contributor

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?

@laurit
Copy link

laurit commented Jun 2, 2023

Otel java agent does not read properties from spring application.properties, try using system properties or environment variables as described in https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure/README.md or in the agent configuration file https://opentelemetry.io/docs/instrumentation/java/automatic/agent-config/#configuration-file

@songy23 songy23 added waiting for author and removed needs triage New item requiring triage labels Jun 5, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Aug 7, 2023

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.

@github-actions github-actions bot added the Stale label Aug 7, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 6, 2023

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants