How to grab older MID Server Agent logs, for when agent0.log.0 entries don't go back far enoughIssue A MID Server record has the Related Link "Grab MID Logs" which will retrieve the current wrapper and agent log from the MID Server, and leave it as an attachment in the ECC Queue. Only agent0.log.0 and wrapper.log will be fetched. However the agent log file contains only the most recent log entries because the logs rotate every 10MB. If you have MID Server debugging turned on during a large Discovery run for example, you may even have less than an hour's worth of logging in that file. Older logs agent0.log.1, agent0.log.2,..., agent0.log.9 will exist in the ~\agent\logs\ folder that you also may need, and this procedure shows an easy way to grab those too.ReleaseThis procedure is now more-or-less obsolete since the introduction of the MID Logs Viewer in New York, and the new related link to go with it. There is a business rule that runs on input, which then creates an output for the older logs.ResolutionOpen a MID Server form and "Grab MID Logs" in the normal way. You are redirected to an ecc_queue list that is filtered for the GrabLogs jobs. Refresh this list until the inputs for agent0.log.0 and wrapper.log appear.Open the Output record for agent0.log.0 in a form, and modify the Name field value "agent0.log.0" to one of the older filenames, such as "agent0.log.1", or anything from 1 to 9.Now click the related link "Run Again". You will now see a new Output for that other agent log file in the ecc_queue. Refresh the list until the input arrives back from the MID Server.