# No logs in elasticsearch while using log\_sending and stdout log level = OFF **URL:** \ **Category:** APM\ **Tags:** java\ **Created:** [June 21, 2023, 1:25pm UTC](https://discuss.elastic.co/t/no-logs-in-elasticsearch-while-using-log-sending-and-stdout-log-level-off/336588 "2023-06-21T13:25:54Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![GeorgeGkinis](https://avatars.discourse-cdn.com/v4/letter/g/ecc23a/32.png) [@GeorgeGkinis](https://discuss.elastic.co/u/GeorgeGkinis)\ **Post date:** [June 21, 2023, 1:25pm UTC](https://discuss.elastic.co/t/no-logs-in-elasticsearch-while-using-log-sending-and-stdout-log-level-off/336588/1 "2023-06-21T13:25:54Z")
**Kibana version** : 8.8.1 **Elasticsearch version** : 8.8.1 **APM Server version** : 8.8.1 **APM Agent language and version** : java 1.39.0 **Browser version** : chrome 114.0.5735.134 **Original install method (e.g. download page, yum, deb, from source, etc.) and version**: maven **Fresh install or upgraded from other version?** fresh **Is there anything special in your setup?** **Description of the problem including expected versus actual behavior. Please include screenshots (if relevant)**: We have activated log\_sending and experimental features is set to true We only see limited logs in kibana from the application, specifically the apm agent logs only. The application writes a lot of logs to files and the sdout (console) level is set to OFF: ```auto logging.stdout wildfly.LoggingCategorySpec stdout OFF ${tag.default} ``` We receive logs only from the apm-agent itself and none of the logs written to the filesystem. ```auto Jun 20, 2023 @ 17:42:51.768 hp-backoffice ERROR Remote configuration is not available. Check the connection between APM Server and Kibana. Jun 20, 2023 @ 15:38:56.511 hp-backoffice WARN com.ibm.as400.access.AS400JDBCConnection uses an unsupported class file version (pre Java 4)) and can't be instrumented. You may try setting the 'instrument_ancient_bytecode' config option to 'true', but notice that it may cause VerificationErrors or other issues. Jun 20, 2023 @ 15:38:56.491 hp-backoffice WARN com.ibm.as400.access.AS400JDBCStatement uses an unsupported class file version (pre Java 4)) and can't be instrumented. You may try setting the 'instrument_ancient_bytecode' config option to 'true', but notice that it may cause VerificationErrors or other issues. Jun 20, 2023 @ 15:38:56.465 hp-backoffice WARN com.ibm.as400.access.AS400JDBCPreparedStatement uses an unsupported class file version (pre Java 4)) and can't be instrumented. You may try setting the 'instrument_ancient_bytecode' config option to 'true', but notice that it may cause VerificationErrors or other issues. Jun 20, 2023 @ 15:38:56.439 hp-backoffice WARN com.ibm.as400.access.AS400JDBCCallableStatement uses an unsupported class file version (pre Java 4)) and can't be instrumented. You may try setting the 'instrument_ancient_bytecode' config option to 'true', but notice that it may cause VerificationErrors or other issues. Jun 20, 2023 @ 15:38:39.401 hp-backoffice INFO Cannot read implementation version based on ProtectionDomain. This should not affect your agent's functionality. Failed with message: URI scheme is not "file" Jun 20, 2023 @ 15:38:39.344 hp-backoffice INFO Cannot read implementation version based on ProtectionDomain. This should not affect your agent's functionality. Failed with message: URI scheme is not "file" Jun 20, 2023 @ 15:38:39.334 hp-backoffice WARN org.apache.commons.httpclient.HttpMethodDirector uses an unsupported class file version (pre Java 4)) and can't be instrumented. You may try setting the 'instrument_ancient_bytecode' config option to 'true', but notice that it may cause VerificationErrors or other issues. Jun 20, 2023 @ 15:38:39.097 hp-backoffice INFO Cannot read implementation version based on ProtectionDomain. This should not affect your agent's functionality. Failed with message: URI scheme is not "file" Jun 20, 2023 @ 15:38:38.693 hp-backoffice INFO Cannot read implementation version based on ProtectionDomain. This should not affect your agent's functionality. Failed with message: URI scheme is not "file" Jun 20, 2023 @ 15:38:38.411 hp-backoffice INFO Cannot read implementation version based on ProtectionDomain. This should not affect your agent's functionality. Failed with message: URI scheme is not "file" Jun 20, 2023 @ 15:38:38.159 hp-backoffice INFO Cannot read implementation version based on ProtectionDomain. This should not affect your agent's functionality. Failed with message: URI scheme is not "file" Jun 20, 2023 @ 15:38:35.583 hp-backoffice INFO Cannot read implementation version based on ProtectionDomain. This should not affect your agent's functionality. Failed with message: URI scheme is not "file" Jun 20, 2023 @ 15:38:35.583 hp-backoffice INFO Cannot read implementation version based on ProtectionDomain. This should not affect your agent's functionality. Failed with message: URI scheme is not "file" Jun 20, 2023 @ 15:38:35.401 hp-backoffice INFO Cannot read implementation version based on ProtectionDomain. This should not affect your agent's functionality. Failed with message: URI scheme is not "file" ... ... ... ``` Does the log\_sending feature only intercept logs going to system out? Is there a way to target specific loggers to be intercepted in our Java code/settings? Maybe this commit can be helpfull: > > > Co-authored-by: Sylvain Juge \ We understand that log\_sending is an experimental feature but comes really handy in our PoC fese of implementing Observability. Thanks. ---
**Author:** ![Jack\_Shirazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_shirazi/32/91641_2.png) [@Jack\_Shirazi](https://discuss.elastic.co/u/Jack_Shirazi)\ **Post date:** [June 21, 2023, 2:00pm UTC](https://discuss.elastic.co/t/no-logs-in-elasticsearch-while-using-log-sending-and-stdout-log-level-off/336588/2 "2023-06-21T14:00:17Z")
Hi, what logging mechanism/framework is being used here? Can you be clearer about the components and versions, eg wildfly version, jdk version, logging framework and version. Thanks ---
**Author:** ![GeorgeGkinis](https://avatars.discourse-cdn.com/v4/letter/g/ecc23a/32.png) [@GeorgeGkinis](https://discuss.elastic.co/u/GeorgeGkinis)\ **Post date:** [June 29, 2023, 11:47am UTC](https://discuss.elastic.co/t/no-logs-in-elasticsearch-while-using-log-sending-and-stdout-log-level-off/336588/3 "2023-06-29T11:47:58Z")
Hello, It seems that our JBOSS server uses the v1 logging library. We will try upgrading to v3.0.0 first. Thanks! ---
**Author:** ![GeorgeGkinis](https://avatars.discourse-cdn.com/v4/letter/g/ecc23a/32.png) [@GeorgeGkinis](https://discuss.elastic.co/u/GeorgeGkinis)\ **Post date:** [June 29, 2023, 1:48pm UTC](https://discuss.elastic.co/t/no-logs-in-elasticsearch-while-using-log-sending-and-stdout-log-level-off/336588/4 "2023-06-29T13:48:04Z")
We also use wildfly 24 and this version is not currently supported: > **[Supported technologies | APM Java Agent Reference \[1.x\] | Elastic](https://www.elastic.co/guide/en/apm/agent/java/current/supported-technologies-details.html#supported-app-servers)** Only wildfly versions 8-16 are tested. We run on Java 11 so we cannot use apm-agent version 1.39.0 it seems.. ---
**Author:** ![Jack\_Shirazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_shirazi/32/91641_2.png) [@Jack\_Shirazi](https://discuss.elastic.co/u/Jack_Shirazi)\ **Post date:** [July 13, 2023, 2:02pm UTC](https://discuss.elastic.co/t/no-logs-in-elasticsearch-while-using-log-sending-and-stdout-log-level-off/336588/5 "2023-07-13T14:02:14Z")
> [@GeorgeGkinis](#): > > Only wildfly versions 8-16 are tested. Although these are tested, we expect the agent to work with later versions, and we are intending to start testing more recent versions > [@](#): > > We run on Java 11 so we cannot use apm-agent version 1.39.0 it seems.. All our agent versions should work on java 11 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 10, 2023, 2:02pm UTC](https://discuss.elastic.co/t/no-logs-in-elasticsearch-while-using-log-sending-and-stdout-log-level-off/336588/6 "2023-08-10T14:02:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.