UNSOLVED Log monitoring configurations are blocked

[TRACEYRAWLINGS]

Log monitoring are blocked but there are no files with .out0, or .log0
in the directory.

I see wlsdm.agent.DEServer1.log_.lck
and i see older log files wlsdm.agent.DEServer1.log
and i see older log files wlsdm.agent.DEServer1.log.1

Which files are we supposed to remove?

[fevzi.korkutata-wlsdmteam]

@traceyrawlings said in Log monitoring configurations are blocked:

Log monitoring are blocked but there are no files with .out0, or .log0
in the directory.

I see wlsdm.agent.DEServer1.log_.lck
and i see older log files wlsdm.agent.DEServer1.log
and i see older log files wlsdm.agent.DEServer1.log.1

Which files are we supposed to remove?

Hi,
These notifications are based on WLDF queries for your WebLogic server logs. If querying WebLogic logs through WLDF tooks long time, this notification visible to WebLogic administrators.
You need to check WebLogic logs not WLSDM logs. Keeping rotated WebLogic (*.out0, *.log0) logs cleaned and tidy would improve your WebLogic domain performance.