Increase Number Of Logs Stored Locally

[Tyler Edmonds]

Hello!
I'm doing some debugging on a batch process and I am finding that the IC2 Log window is rolling over too many logs and I'm losing the ones that have the context I need. 

Example: In my org, I go click the button that starts my process, it kicks off a large batch process that creates a ton of logs and theere are other things going on as well that are generating logs. By the time the process is done and I go to inspect the list of logs available in the IC2 log viewer, I notice that the logs I want are gone.  Only the most recent ~50 or so are visible in the log list. 

I can filter a bit for them but that's not super helpful when I need logs around it.  

- looking for a Batch Log that has rolled off > easy enough to filter on Batch and find it. 

- now I want the /aura log directly before that Batch start log, but un-filtering at that point just takes me back to the top of the list. There are a bajillion aura logs, so filtering on /aura doesn't help narrow it down at all. 

Is there a way to increase the number of logs that show visible in the list? 

Or a better way to filter than I'm doing it? 

Thank you!

[Scott]

Hi. IC doesn’t store logs locally, though you can download logs locally if you’d like. It queries the most recent (up to) 100 log headers and presents them, and when you double-click or press Enter on a log header, that log body is downloaded for presentation in the Log Analyzer, though not to local disk. If you’re only seeing 50, that means to me that perhaps Salesforce is rolling your logs in the org. Or do you see more than 50 there?

If it helps, the query that IC executes to populate the log headers is:

SELECT Id, Application, LogUser.Username, LogUser.Name, Operation, StartTime, LastModifiedDate, DurationMilliseconds, Status, Location, LogLength FROM ApexLog ORDER By StartTime DESC LIMIT 100

Let me know if that doesn’t help.

Regards,
Scott Wells

​