We recently upgraded to release 21.2.8;
When we take a look at the log folders it looks like this:
bash-4.2# ls -lhtr DM/logs/
total 379M
-rw-r--r-- 1 root root 11M Apr 8 21:22 DMService.log.2022-04-08.2
-rw-r--r-- 1 root root 2.6M Apr 8 23:58 DMService.log.2022-04-08.3
-rw-r--r-- 1 root root 11M Apr 9 10:48 DMService.log.2022-04-09.1
-rw-r--r-- 1 root root 11M Apr 9 21:20 DMService.log.2022-04-09.2
-rw-r--r-- 1 root root 2.5M Apr 9 23:59 DMService.log.2022-04-09.3
-rw-r--r-- 1 root root 11M Apr 10 09:40 DMService.log.2022-04-10.1
-rw-r--r-- 1 root root 11M Apr 10 20:22 DMService.log.2022-04-10.2
-rw-r--r-- 1 root root 3.5M Apr 10 23:59 DMService.log.2022-04-10.3
-rw-r--r-- 1 root root 11M Apr 11 10:37 DMService.log.2022-04-11.1
-rw-r--r-- 1 root root 11M Apr 11 21:20 DMService.log.2022-04-11.2
-rw-r--r-- 1 root root 2.6M Apr 11 23:59 DMService.log.2022-04-11.3
-rw-r--r-- 1 root root 11M Apr 12 10:35 DMService.log.2022-04-12.1
-rw-r--r-- 1 root root 11M Apr 12 21:01 DMService.log.2022-04-12.2
-rw-r--r-- 1 root root 2.9M Apr 12 23:59 DMService.log.2022-04-12.3
-rw-r--r-- 1 root root 3.7M Apr 13 23:59 DMService.log.2022-04-13
-rw-r--r-- 1 root root 7.9M Apr 14 23:59 DMService.log.2022-04-14
-rw-r--r-- 1 root root 8.6M Apr 15 23:59 DMService.log.2022-04-15
-rw-r--r-- 1 root root 8.1M Apr 16 23:59 DMService.log.2022-04-16
-rw-r--r-- 1 root root 6.8M Apr 17 23:59 DMService.log.2022-04-17
-rw-r--r-- 1 root root 8.8M Apr 18 23:59 DMService.log.2022-04-18
-rw-r--r-- 1 root root 9.8M Apr 19 23:59 DMService.log.2022-04-19
-rw-r--r-- 1 root root 8.4M Apr 20 23:59 DMService.log.2022-04-20
-rw-r--r-- 1 root root 9.0M Apr 21 23:59 DMService.log.2022-04-21
-rw-r--r-- 1 root root 8.5M Apr 22 23:59 DMService.log.2022-04-22
-rw-r--r-- 1 root root 9.3M Apr 23 23:59 DMService.log.2022-04-23
-rw-r--r-- 1 root root 6.7M Apr 24 23:59 DMService.log.2022-04-24
-rw-r--r-- 1 root root 24M Apr 24 23:59 wrapper-20220424.log
-rw-r--r-- 1 root root 26M Apr 25 23:59 wrapper-20220425.log
-rw-r--r-- 1 root root 7.8M Apr 25 23:59 DMService.log.2022-04-25
-rw-r--r-- 1 root root 8.0M Apr 26 23:59 DMService_request_2022_04_26.log
-rw-r--r-- 1 root root 3.6M Apr 26 23:59 DMService.log.2022-04-26
-rw-r--r-- 1 root root 20M Apr 26 23:59 wrapper-20220426.log
-rw-r--r-- 1 root root 8.5M Apr 27 23:59 DMService_request_2022_04_27.log
-rw-r--r-- 1 root root 6.9M Apr 27 23:59 DMService.log.2022-04-27
-rw-r--r-- 1 root root 24M Apr 28 00:00 wrapper-20220427.log
-rw-r--r-- 1 root root 8.7M Apr 28 23:59 DMService_request_2022_04_28.log
-rw-r--r-- 1 root root 7.2M Apr 28 23:59 DMService.log.2022-04-28
-rw-r--r-- 1 root root 25M Apr 29 00:00 wrapper-20220428.log
-rw-r--r-- 1 root root 4.8M Apr 29 06:05 DMService.log
-rw-r--r-- 1 root root 6.8M Apr 29 06:05 wrapper-20220429.log
-rw-r--r-- 1 root root 1.9M Apr 29 06:06 DMService_request_2022_04_29.log
So since the upgrade only one log file is written instead of three. When taking a look at one specific file, e.g. DMService.log.2022-04-24 the file starts with the following line
INFO | Thread-13579 | 2022-04-24 15:11:38,815 | com.ca.im.portal.dm.inventory.Inventory2WSImpl
| InventoryWS (273936) item count of table items: 0
and ends with this line
INFO | pool-3-thread-1 | 2022-04-24 23:59:41,832 | com.ca.im.portal.dm.productsync.GlobalSync
| Global interface Items Synchronization starting
So all logs from 2022-04-24 00:00:00 until 2022-04-24 15:11:38 are missing. Seems like there is an issue with log rotation.
Log files not being rotated or removed from CAPC/NetOps Portal
Log file rotation not working on CAPC/NetOps Portal
Release : 21.2
Component : Performance Management Installations
Defect DE534659
This issue has been corrected in DX Netops Performance Management 21.2.12 and later:
Symptom: The NetOps Portal, DM, EM and SSO Service log files would be overwritten when log rotation happens based on size, leaving only 1 log per day.
Resolution: With this fix, the DX NetOps Performance Management services rotate logs nightly and create files during the day when hitting 10MB per log limit.
(21.2.12, DE534659, 33102367,33126350)
There should be no information lost;
wrapper log should contain all data from all DMService logs