Most of the VF pages in my company org use remote actions, so in debug log the operation is coming as VFRemoting. I need to open many log files to find out the Apex class that has the remote action method I am interested in. For ex, If I need to view the Sytem.debug value recorded using a remote action in controller A, I need to open a few log files and apply filter for Controller A. Is there a way available to search for a word in all the log files shown to me in the log section?
[SalesForce] Search a word in all the log files in developer console
Related Solutions
If it has been a little while since you used it, it stops updating the list with new logs. You can click on "Resume updating" which appears in the top list of buttons just to the right of where you can enter anonymous apex. (The button only appears when it has stopped updating the log list)
If you use something like the Chrome developer tools when running the "Search in Files" functionality you will see the REST API call going out to the web services.
After URL decoding the SOSL query is:
FIND {Foo} IN ALL FIELDS RETURNING ApexClass(id, name, namespaceprefix, body), ApexTrigger(id, name, namespaceprefix, body), ApexPage(id, name, namespaceprefix, markup), ApexComponent(id, name, namespaceprefix, markup)
ApexComponent is labelled "Visualforce Component", so in theory it should be searching the VF components as well.
I confirmed that it can indeed find known content in a VF Component.
However, it was a bit hit and miss about what it would actually find. Other terms that I know appear in the markup didn't come back in the results.
As Mike commented, pulling down the metadata and then searching it locally with the tool of your choice may be the best option.
Best Answer
It isn't currently possible (Summer '17) to use the native tooling to perform a search over the contents of all the log files.
You can do SOSL searches over the body of Apex classes and Triggers, but that isn't going to find you content in a Debug Log.
Searching over the Debug log content would require pulling the bytes of each log down and then searching them locally.
Update: I'd seen some posts recently about using the SFDX command line and GREP over the last N logs. It will still need to pull down the entire log(s).
See Streaming Debug Logs to your console