You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2022/06/24 17:38:42 UTC
[GitHub] [accumulo] dlmarion opened a new issue, #2785: Micrometer and OpenTelemetry logging
dlmarion opened a new issue, #2785:
URL: https://github.com/apache/accumulo/issues/2785
When Micrometer is enabled and configured in Accumulo, but the metric destination is not reachable, a warning is made in the log frequently.
```
2022-06-24T17:26:23,227 [channel.FluxReceive] WARN : [29ae5f57, L:/127.0.0.1:59110 - R:127.0.0.1/127.0.0.1:8125] An exception has been observed post termination, use DEBUG level to see the full stack: java.net.PortUnreachableException: readAddress(..) failed: Connection refused
```
When OpenTelemetry is enabled and configured in Accumulo, but the trace span destination is not reachable, messages are printed in the log:
```
[OkHttp http://localhost:14250/...] ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Failed to export spans. The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:14250
[OkHttp http://localhost:14250/...] ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Failed to export spans. The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:14250
[OkHttp http://localhost:14250/...] ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Too many log messages detected. Will only log once per minute from now on.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [accumulo] dlmarion closed issue #2785: Micrometer and OpenTelemetry logging
Posted by GitBox <gi...@apache.org>.
dlmarion closed issue #2785: Micrometer and OpenTelemetry logging
URL: https://github.com/apache/accumulo/issues/2785
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [accumulo] dlmarion commented on issue #2785: Micrometer and OpenTelemetry logging
Posted by GitBox <gi...@apache.org>.
dlmarion commented on issue #2785:
URL: https://github.com/apache/accumulo/issues/2785#issuecomment-1165797458
Regarding the Micrometer issue, my Accumulo setup is configured to use the Micrometer [StatsD](https://github.com/micrometer-metrics/micrometer/tree/main/implementations/micrometer-registry-statsd) registry and it uses Flux to send the messages. Other registry implementations may use a different mechanism to send metrics, so I don't think modifying our logging configuration to suppress these messages makes sense. The end user can do that if they wish.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [accumulo] dlmarion commented on issue #2785: Micrometer and OpenTelemetry logging
Posted by GitBox <gi...@apache.org>.
dlmarion commented on issue #2785:
URL: https://github.com/apache/accumulo/issues/2785#issuecomment-1165840291
I have been unable to modify the OpenTelemetry logging and I think the reason why is that I'm using the java agent. I added `-Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager` as specified in the Log4j2 [user guide](https://logging.apache.org/log4j/2.x/log4j-jul/index.html) and modified the logging properties to turn the `io.opentelemetry` loggers `off`. It's not working, I think, because the java agent starts logging before the Log4j2 configuration is read. The output contains:
```
./accumulo-cluster start
OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended
[main] INFO io.opentelemetry.javaagent.tooling.VersionLogger - opentelemetry-javaagent - version: 1.14.0
2022-06-24 18:38:37,221 main INFO Registered Log4j as the java.util.logging.LogManager.
...
```
I think that it's possible to modify the logging when *not* using the java agent.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org