Querying the logs is very useful for troubleshooting and observability.
See #215.
Right now we are using jq for that. There are a couple friction points with that.
There are multiple log files and multiple sets of logs (RunMe vs. Foyle)
As a result users are prone to search the wrong logs
jq is overly flexible and its hard to remember the correct syntax and flags (e.g. "-c", vs "-s"). Using "select" vs. "map".
I think we should support a query syntax similar to what Google Cloud Logging Supports.
I think we can support a subset of it and then increase it over time. Here's what we should support
A timestamp range to filter
We should support relative ranges e.g. -1hour
Exact matches on fields
That would make it easy to support most of the queries in #215.
I think we can return the results as a list of strings containing the log entries.
Querying the logs is very useful for troubleshooting and observability. See #215.
Right now we are using jq for that. There are a couple friction points with that.
I think we should support a query syntax similar to what Google Cloud Logging Supports. I think we can support a subset of it and then increase it over time. Here's what we should support
That would make it easy to support most of the queries in #215.
I think we can return the results as a list of strings containing the log entries.