Central Management - Scan Size of logs going into Depolyment_step_result_messages_processing Folder

[ryanrichter94]

What You Are Seeing?

When using the CCM API to do a deployment the --no-output switch is not appended to all choco install/upgrade commands written. This is causing a lot of excess data to be entered in the log as progress output on downloads of packages. Thus creating large log files in the Depolyment_step_result_messages_processing folder. This causes a big slowdown in deployments where they stay open as active for extended periods of time while the service tries to interpret the log and write the necessary data to the CCM DB.

Possible solution

My suggestion would be to check for the xml file size before processing it and put the xml-record in a fault-queue when it is bigger than .. (1MB?).

References

• ZenDesk Ticket

┆Issue is synchronized with this Gitlab issue by Unito