Capturing application logs does not work.

[gabrielSanchezCampello]

Describe the bug

I am running an Oracle Weblogic Server with the java agent and it only detects and loads the weblogic logs while not detecting/ignoring those of the applications deployed on it.

The application traces are being collected correctly, it is only the logs generated by the application that are not captured. By the way, the applications send the logs to a different file than weblogic.

Steps to reproduce

To reproduce it, you only need to run an Oracle Weblogic Server and deploy applications on it that save the logs in files other than the weblogic.

Expected behavior

The expected behavior would be that the agent captures the application logs as it does with the traces in order to correlate them.

Actual behavior

The current behavior is that the agent does not capture application logs.

Javaagent or library instrumentation version

v.2.12

Environment

Additional context

No response

[raghanag]

hi @gabrielSanchezCampello I am also experiencing the same issue with traces, we are using weblogic version 14.1.2.0.0 and have below configuration in java_options but not able to see any traces or spans from basic HttpServlet, Filter, or javax.servlet.* classes
Are you able to see traces?

-Dotel.javaagent.configuration-file=/sphere/conf/agent_config.properties
-javaagent:/sphere/otel/opentelemetry-javaagent.jar

and agent_config.properties

otel.metrics.exporter=prometheus
otel.exporter.prometheus.port=8089
otel.traces.exporter=otlp
otel.logs.exporter=none
otel.service.name=cpq
otel.exporter.otlp.traces.protocol=http/protobuf
otel.exporter.otlp.traces.endpoint=http://sphere-jaeger-agent.sphere-platform:4318/v1/traces

[laurit]

@gabrielSanchezCampello what logging framework you are using? If you can't see the application logs then could be that you are using a logging framework that we don't support or for some reason our instrumentation does not work for your application. A minimal sample application that reproduces the issue would help. Preferably this application should not require weblogic.

[gabrielSanchezCampello]

hi @laurit
I think the problem is that the agent is only instrumenting the WebLogic logger that sends all its logs to an ‘.out’ file. Meanwhile, each application is implementing its own loggers/appenders that send their logs to different files.
Does this behaviour make sense to you?

We are using log4j-1.2.17.

Regards