Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
How to grab older MID Server Agent logs, for when agent0.log.0 entries don't go back far enough - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • How to grab older MID Server Agent logs, for when agent0.log.0 entries don't go back far enough
KB0685661

How to grab older MID Server Agent logs, for when agent0.log.0 entries don't go back far enough


6357 Views Last updated : Jan 3, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

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.

Release

This 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.

Resolution

  1. Open 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.




  2. 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.





  3. 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. 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.