cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Lot of logs in /opt/dynatrace/oneagent/log/java dir

imoskovko1
Inactive

Hello!

Customer noticed lot of log files in

/opt/dynatrace/oneagent/log/java

few example lines are:

-rw-r--r--. 1 root root 23031 Mar 8 13:45
1-service.jar_***-service-__1(101).0.log


-rw-r--r--. 1 root root 23532 Mar 8 14:02
ruxitagent_***-service.jar_***-service-__1(102).0.log

-rw-r--r--. 1 root root 23475 Mar 8 14:11
ruxitagent_***-service.jar_***service-__1(103).0.log

-rw-r--r--. 1 root root 23532 Mar 8 14:28
ruxitagent_***-service.jar_***-service-__1(104).0.log

-rw-r--r--. 1 root root 23475 Mar 8 14:47
ruxitagent_***-service.jar_***-service-__1(105).0.log

-rw-r--r--. 1 root root 23532 Mar 8 15:06
ruxitagent_***-service.jar_***-service-__1(106).0.log

-rw-r--r--. 1 root root 23475 Mar 8 15:20
ruxitagent_***-service.jar_***-service-__1(107).0.log

-rw-r--r--. 1 root root 23532 Mar 8 15:33
ruxitagent_***-service.jar_***-service-__1(108).0.log

What is is and how to suppress it generation or rotate?

Regards,

Igor


5 REPLIES 5

Julius_Loman
Leader

These are logs from oneagent residing in a java process. As soon as it starts, it gets instrumented and log will be created. If it is a process you don't want to monitor, just set this up in Dynatrace either for this process group or setup a deep monitoring rule to skip monitoring of the avtocod-service processes. If this is not a one shot process starting every few minutes, then look at the contents of the log (you can download the logs using "Download support archive" for the host in the menu).

Oneagent does log rotation and pruning, so you won't run out of space.


imoskovko1
Inactive

Thank you Julius! We will take close look at file contents and creation dynamics...


imoskovko1
Inactive

Actually customer clarified details

In OpenShift pod of service-aggregator service

there are log files from other pods services:

ruxitagent_jdbc-adapter.jar_jdbc-adapter-****-ro-__1.0.log

ruxitagent_****-mobile-****-service.jar_****-mobile-****-service-__1.0.log

ruxitagent_filestore-service.jar_filestore-service-__1.0.log

ruxitagent_****-service.jar_****-service-__1(191).0.log

and it looks incorrect.

**** i have masked some names ...


That's correct I believe since the Oneagent is in fact installed on the host where containers are running (although running in a container). The agent folders are shared between all processes on the host -> thus logs from processes from other pods running on the same host will appear.


Hello Julius. After discussing proposed by you explanation with customer he accepted it. Thank you very much for help!

Best regards, Igor

p.s.

Also found usefull discussion :

https://answers.dynatrace.com/spaces/482/dynatrace-open-qa/questions/177348/deploy-ruxit-agent-as-a-container.html

«despite running in the container all of the oneagent files are actually placed on the host's filesystem, not in a filesystem of the container"