[feature] Search functionality in Traces/Logs/Errors

[stargazer33]

STEP1:

My client application connected to Plexus.
In logfile of this application I see some error and the x-request-id=44158a26-55d4-43aa-8120-a93f48f95190 and this x-request-id comes from Plexus

STEP2:

I go to Plexus and want to find out what actually happened.
What was actually sent to provider?

PROBLEM:

I can not find this request!

PROPOSED SOLUTION:

Some sort of search functionality would be great!

[stargazer33]

Yes, there is a workaround: I can create backup, extract the archive and search in .csv files... (found something in debug_logs.csv)
But... built-in search would be much better!

ADDITIONAL feature: it would be absolutely great to select a record in Traces/Logs/Errors and to export it in curl format!
This will save a lot of time!
This is a standard procedure—you try to demonstrate a problem to a LLM provider: curl is a universal way to do that.

[mcowger]

Giving them the JSON is the standard way - they don't need a curl command.

I'd accept a PR for adding a search option if you would like to contribute it.