-
Notifications
You must be signed in to change notification settings - Fork 855
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
How to suppress export logs in open-telemetry agent? #5347
Comments
This looks like an issue for AWS, not for the general opentelemetry java libraries. Or possibly for the opentelemetry-java-instrumentation project where the vanilla agent code lives. |
The logs samples you posted don't look like they are produced by the upstream agent. Consider filing an issue in the https://github.com/aws-observability/aws-otel-java-instrumentation project first, maybe they'll recognize what emits these logs. |
@mateuszrzeszutek @jkwatson Just I created a ticket in aws repository. But a generic question, setting "OTEL_LOG_LEVEL=ERROR" doesn't fix the above issue? This ticket discussed the log_level. I want to see the log line only if there is any error in exporting otherwise I don't need log_level I believe we can achieve this using "OTEL_LOG_LEVEL=ERROR" |
The Java SDK doesn't support that property, nor will it probably going forward, since the SDK uses JUL and the log level can be configured for that directly. |
These log lines look like access logs generated in server side. I'm suspecting that the logs are being generated from a different workload that is sharing the same pod as the java application. I'm posting here just to request help in one matter: does java http client libraries like okhttp would be able to produce access logs like these? |
I just confirmed with @VelDeveloper and the log entries are coming from istio. Ref: https://istio.io/latest/docs/tasks/observability/logs/access-log/#test-the-access-log |
can we close this issue, then? |
The issue aws-observability/aws-otel-java-instrumentation#369 (comment) was closed, so I assume yes. |
closing as not-relevant for this repository. |
I am using "aws-opentelemetry-agent" for my spring-boot application and we are exporting logs & traces via gRPC.
whenever it exports it generates a log line like below. These logs line blow up the logging system since we export them more often.
Can I suppress this log message? I want error logs whenever the export fails.
Steps to reproduce
FROM maven:3.8.3-openjdk-17-slim
RUN mkdir -p /agent
RUN apt-get update && apt-get install -y wget
RUN wget -O /agent/aws-opentelemetry-agent.jar https://github.com/aws-observability/aws-otel-java-instrumentation/releases/latest/download/aws-opentelemetry-agent.jar
ENV JAVA_TOOL_OPTIONS="-javaagent:/agent/aws-opentelemetry-agent.jar
-Dotel.resource.attributes=service.name=sample
-Dotel.propagators=tracecontext
-Dotel.traces.exporter=otlp
-Dotel.exporter.metrics.endpoint=http://sample:4317
-Dotel.exporter.traces.endpoint=http://sample:4317
-Dotel.metrics.exporter=otlp"
VOLUME /srv/logs
ARG JAR_FILE
COPY ${JAR_FILE} sample.jar
ENTRYPOINT ["java","-jar","/sample.jar"]
What version and what artifacts are you using?
we are using the latest aws-opentelemetry-sdk
Environment
Environment: AWS EKS
The text was updated successfully, but these errors were encountered: