✨ feat: Search engine to look for an error or message in the org's debug logs

[AnibalGarcia]

Is your feature request related to a problem?

When we run a process and several debug logs are generated, we never know which one contains the error or issue we are looking for. We have to open all of them one by one to find it.

This is a very tedious task. Also, when using the tool's command to access the org's debug logs.

Describe the solution you'd like

A search engine could be implemented to look for an error or message in the org's debug logs. The tool would allow us to download the debug log that we are looking for directly.

Describe alternatives you've considered

This could be done in the tool's existing command or by creating a new one (if it improves the user experience).

Additional context

This idea was given to me by an attendee of my talk about Apex Log Analyzer at Polish Dreamin’ 2025.

[lcottercertinia]

@AnibalGarcia Great idea!
Adding some thoughts for later.
The ApexLog content is not queryable on the ApexLog table.
The content is retrieved via something like /sobjects/ApexLog/{id}/Body we use the sf node libraries to do this.
As such there is no way to query using SOQL/SOSL on the content of the ApexLog.

To do this we would have to download the logs are search the content.
We could display the first bit of matching text underneath the last line of content in the log list
For example if searching for "CPU" in a large debug statement of "_CPU_LIMIT" we could show as
"**CPU**LIMIT"