The disk is being filled, and the biggest contributors are .ibd files (events) that seem to come from the Mysql database in the Netops Portal (../mysql/data/em directory), eg:
mysql mysql 2.9G /opt/CA/MySql/data/em/event_properties#P#p20210427.ibd
mysql mysql 3.4G /opt/CA/MySql/data/em/event_properties#P#p20210428.ibd
mysql mysql 2.6G /opt/CA/MySql/data/em/event_properties#P#p20210429.ibd
mysql mysql 4.7G /opt/CA/MySql/data/em/events_l10n#P#p20210427.ibd
mysql mysql 5.7G /opt/CA/MySql/data/em/events_l10n#P#p20210428.ibd
mysql mysql 4.4G /opt/CA/MySql/data/em/events_l10n#P#p20210429.ibd
mysql mysql 1.2G /opt/CA/MySql/data/em/events#P#p20210427.ibd
mysql mysql 1.4G /opt/CA/MySql/data/em/events#P#p20210428.ibd
DX Netops Performance Management any release
By default, the Event Manager database retains events for 30 days.
How long the Event Manager stores or retains events is controlled by the Event.Retention property in the em.properties file
There is an attribute called Event.Retention (/opt/CA/PerformanceCenter/EM/webapps/EventManager/WEB-INF/em.properties file) in the Event Manager database that controls the event retention settings.
By reducing the Event.Retention (30 days by default) it should remove .ibd files older than the specified retention setting, and therefore, it should free disk space, e.g.:
db.driverClassName=com.mysql.jdbc.Driver
db.timeout=120
db.maxActive=40
rib.queryTimeout=100
em.ws.maxqueue=50
Event.Retention=15
db.url=jdbc\:mysql\://localhost\:3306/em?useUnicode\=true&characterEncoding\=UTF-8
Once the Event.Retention is updated, we would need to wait until midnight for MySQL db re-periodization to occur and should take care of the old .ibd files accordingly.