Generate a master log file of all client log files.
There is a lot of very detailed information in the individual component client logs files, But with all that detail in so many logs, it can be difficult to tell what the client is doing at any given time. I would like to see a master log of all the high level client activity and timestamps.
12:00 hardware inventory started
12:02 hardware inventory complete
12:05 policy download
12:08 software inventory started
etc...
It would help narrow down the number of logs to examine and the timeframes to look at.
Michael Honeycutt
shared this idea
8 comments
-
Mike
commented
A log file would be great, but for me a SQL table would be better so that I can query or use a report for the information without needing access to the local device.
-
Anonymous
commented
I secondary this.
Not only text logs but WinEvent logs should be implemented.
This is needed for automation and orchestration.
Triggering schedules using WMI method isn't enough - I need to ensure that the cycle was completed successfully. -
Jason Sandys
commented
To be clear, not every little line from all of the client logs needs to added, just the "major" events as outlined in the original post.
-
Jason Sandys
commented
This would be even better as events in a Windows event log.
-
Matt
commented
no, I agree with a master log file - this will benefit MSFT CSS Support Teams for scouring through multiple logs.
-
Amy Ahlberg
commented
We need a central log with abbreviated items in addition to all of the detailed logs for more in depth troubleshooting for our level 1 and level 2 support areas. Our level 3 ticket volume is out of control as tickets cannot be closed at level 1 and level 2 due to the complexity of troubleshooting deployments. We have approx. 260 support staff in level 1 and level 2. Training them to read these logs hasn't worked.
-
Anonymous
commented
You should see what the log file looks like for Linux machines with the CM agent installed. Yes we are the only company I have ever heard of using the CM agent on Linux in an enterprise environment. Everything is in one file, and its a mess. Now its not condensed and high level, but we would love to have separate log files for Linux, or at least less noise in the one we have.
-
Will
commented
Use CMTrace to open all the relevant log files and select the 'merge' option..