Zip the Communication logs larger than xy MBs

Zip the Communication logs larger than xy MBs

We have several discovery jobs that when run with or without results included can create huge Communication logs well over 100MBs.

Those Communication logs (CommLogs) can't be requested in the UI as they will fail to be downloaded in a timely manner from the probe to the server to the UI Client.

Such big CommLogs are also problematic on the DFP disk as they will be stored in the runtime\Communication Logs directory, and if they aren't cleaned from time to time they can lead to insufficient DFP storage.

The proposal is to set a limit (configurable or not) after which a Communication log will be zipped on the DFP disk in the same directory DataFlowProbe\runtime\Communication Logs. This CommLogs can't be viewed over the UI, only to be downloaded.

In general we have such problems with CommLogs from discovery jobs that run in a separate process and report back a big topology over 100k CIs like vCenter Topology by VIM job.

 

Tags (4)
1 Comment
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.