A very common case (for us) is to locate an entry in a stream, find its correlation id (we use end-to-end tracing with correlation ids that match [almost] all the way from frontend to database level), then search for all records that match this ID. Currently, we use the "zoom in" button, then scroll up to search query, cut the newly added part, switch to another browser tab that has generic search open for the same range and then paste the query. This feels a bit awkward and I believe that we're not the only ones that are inconvenienced with this.
While the solution is very user-specific, I propose adding another option for stream-based searches (along with "Create extractor for ..." and "Show terms of ..."): "Search everywhere for ...". This should open another page/tab with the specified query fragment applied to all messages, probably copying over the shared query parts like time range.
Ideally I would suggest adding some kind of extensibility mechanism for such "cross-searching", but I believe it would be too much of an effort for now, while there are other more valuable features waiting to be implemented.
A very common case (for us) is to locate an entry in a stream, find its correlation id (we use end-to-end tracing with correlation ids that match [almost] all the way from frontend to database level), then search for all records that match this ID. Currently, we use the "zoom in" button, then scroll up to search query, cut the newly added part, switch to another browser tab that has generic search open for the same range and then paste the query. This feels a bit awkward and I believe that we're not the only ones that are inconvenienced with this. While the solution is very user-specific, I propose adding another option for stream-based searches (along with "Create extractor for ..." and "Show terms of ..."): "Search everywhere for ...". This should open another page/tab with the specified query fragment applied to all messages, probably copying over the shared query parts like time range. Ideally I would suggest adding some kind of extensibility mechanism for such "cross-searching", but I believe it would be too much of an effort for now, while there are other more valuable features waiting to be implemented.