Currently, the Chocolatey Agent log does not refer to its host by its Computer Name; it references itself as 'this computer'. Please see the line pulled from a customer log below.
2024-05-06 10:05:21,833 48 [INFO ] - Check for deployment step found an active step (tag:34) to perform for this computer.
If this could be changed to include the Computer Name so that the host is easily identifiable, that would be of great benefit. It would also be helpful at the top of the Chocolatey Agent log where it's bootstrapping if the Computer Name could be listed there. That would allow us to know which machine we're troubleshooting immediately.
Why Is It Needed
There are times when the Support staff ask for logs and when we receive them, we may get several logs from several machines that are either not named, or have been named vaguely. It would make it much simpler to troubleshoot issues if we could match Chocolatey Logs and Chocolatey Agent logs, as well as CCM-Service Logs and Chocolatey Agent logs without customer intervention.
Description
Currently, the Chocolatey Agent log does not refer to its host by its Computer Name; it references itself as 'this computer'. Please see the line pulled from a customer log below.
2024-05-06 10:05:21,833 48 [INFO ] - Check for deployment step found an active step (tag:34) to perform for this computer.If this could be changed to include the Computer Name so that the host is easily identifiable, that would be of great benefit. It would also be helpful at the top of the Chocolatey Agent log where it's bootstrapping if the Computer Name could be listed there. That would allow us to know which machine we're troubleshooting immediately.
Why Is It Needed
There are times when the Support staff ask for logs and when we receive them, we may get several logs from several machines that are either not named, or have been named vaguely. It would make it much simpler to troubleshoot issues if we could match Chocolatey Logs and Chocolatey Agent logs, as well as CCM-Service Logs and Chocolatey Agent logs without customer intervention.
┆Issue is synchronized with this Gitlab issue by Unito