logs

[frankbe]

Hi,

i have still no data in table plugin_p4a_chocolatey_update_log
in which script the data should be written ?

on the agent itself i see in c:\ProgramData\chocolatey\logs\ that there were update e.g. on firefox

[Cubert]

That's accurate.
Currently, update logging is limited to the notice of execution and is recorded in the main logs table: plugin_p4a_chocolatey_logs.




I have a weekly scheduled update set for these agents

Screenshot 2025-05-01 095736.png (45.94 KiB) Viewed 987 times

.



How updates work.

1. You set a schedule or by default enabled agents update daily

• Based on schedule the Automate backend will send a command to online and enabled agents to "choco update all"

• Agent log is updated that updates were sent to agent as a command.

At one point, we were updating packages individually, but we found that this led to a higher failure rate due to package dependencies, script schedules being affected or delayed by local agent time, and a few other Automate annoyances.

So to lower the load on the Automate Host and to speed up the process of updates we now send the agents a direct command to update verses scheduling a script, executing a script, processing each script function and logging the results.

We also improve the command process by allowing the agent's command to be pushed down and released so that Automate does not have to monitor and track the commands progress and process any results. The command creates its own process on agent and releases Automate's command threads. This greatly speeds up the processing of updates across large MSPs (2000 agents+).

[frankbe]

I anderstand, that sending "update all" is faster and more efficient than sending an update command for single packages -
but we (our customers) need a report, about the progess of updating during the month.
It would help, if you save the list of managed application with the version numbers of the packages with a date on a daily schedule
So i can look and compare the list and version numbers per day oder per month. a retention with 3 month would be enough for us, so that there is not too much space the table uses in the database,

[Cubert]

Let me see about adding to the log, a list of any packages that current show as out of date at the time we run update all.