Idea ID 1791130
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.