How to search all MID Server logs at once, in situ, and return just the results back to the instanceDescriptionMID Server logs are rotated every 10MB, and for the agent logs there are 10 of them. Without downloading them all, you can't know the date cut-offs and so can't know which file you want. This trick avoids doing that, by getting the MID Server to search all its logs itself for a string you are looking for. e.g. The sys_id of a specific ECC Queue output record, to find the agent log entries for the thread that ran itAn error message, to see if it has occurred beforeAll "LogStatusMonitor" entries, to get e.g. a full record of memory usageResolution The basic idea is to use the "Command" probe to run "find" on the logs folder, to return any lines in any file that contain the string. Open a new blank ECC Queue record form - /ecc_queue.doFill in the fields like so: Agent = mid.server.<MID Server name>Topic = CommandName = FIND "<search string>" logs\*.*Queue = OutputState = ReadySequence = (clear this value) SubmitLook in the ECC Queue table for the Input response from that output. The output from the commands will be in the Payload./ecc_queue_list.do?sysparm_query=topic%3dCommand For Linux MID Servers, a similar search can be run with grep. Example: The following is the output from searching for a specific ecc_queue output record sys_id "f3b7c62f1b937b840c50524d6e4bcb5f". In this case it was a Discovery SNMP probe, but the logs from any feature or probe could be searched in the same way, because the thread name will always include the output sys_id.