search

Agoric / causeway

https://causeway.agoric.net/
0 stars 1 forks source link

start with any search string such as offer id #11

Open dckc opened 2 weeks ago

dckc commented 2 weeks ago

As a user, I want to enter a search term and have everything before the 1st occurrence of that term filtered. (everything except the parts of the slog file that give vat names)

For example, the precipitating event in my Aug 23 case was proposing a DebtLimit change. Like all smart contract interactions, the relevant transaction has an OfferSpec including an id. The user could provide the id, and the service would find where that id shows up and extract from there for the following 10 or 20 seconds.

rabi-siddique commented 1 week ago

This seems very cool. Do you think we should add a Next button on the UI to load logs in 20-second intervals for easier navigation? I think that can help in quickly viewing logs in manageable 20-second chunks.

dckc commented 1 week ago

a Next button does seem like a straightforward enhancement.

I don't recall any specific situations where it would have been useful, but if someone were looking at a phenomenon that takes longer than a few blocks, then yes, it would be handy.

dckc commented 1 week ago

Also: this request for "start by searching for a string" was assuming that the user always uploads a file.

I don't know whether it's feasible when the tool gets logs from emerynet or the like.

mhofman commented 1 week ago

With the new contextual slog sender in u18, we may want to enable search by trigger info (e.g. txHash). The event of the same trigger may span across multiple blocks.

rabi-siddique commented 1 week ago

Also: this request for "start by searching for a string" was assuming that the user always uploads a file. I don't know whether it's feasible when the tool gets logs from emerynet or the like.

It’s feasible. Currently, when fetching testnet logs for a block height query, we search logs within this 90-day range. I believe I can replicate a similar approach for user search terms. The main thing would be to update the Logs Explorer query and determine which time limit (90, 60, or 30 days) offers the best performance.