Log Searching, Order, and Context

[randy-girard]

Hello. Is it possible to do any of the following:

• Reverse the order in which the logs show.
• When you search for something, can it search all history (infinite scroll?) and not just the time window you are looking at?
• Have it default to BODY contains if you just search for something quickly, on pushing enter, instead of it creating the "body contains ****" item.
• Is it possible to have the search results just go to each matched result, instead of only showing the matched results? Next/Previous through the matches. I know there is context window, but it would be handy to just see it right in the main window.

[nityanandagohain]

• Yeah you can change the orderby to timestamp asc, I have attached a screenshot
• No as of now we just do it in the window selected, otherwise it will create confusion. You can select a bigger timerange and search. Please share if there is a different usecase for this.
• As of now we do support this, but It is not consistant always eg:- if you enter just a single word then you have to press enter twice for it be converted to body contains '' , if there are multiple words then just pressing enter works. Hopefully this will be fixed in the next version of query builder. cc @srikanthccv
• Hi please let me know if this solves it for you feat: logs explorer context log line redirection #7142 (comment) . You will have to click on the log line in the context page. Though happy to here more on this.

[randy-girard]

• I guess I was more curious in the live view. Having logs stream in the order they come in, kind of like tailing a log file.
• It seems like the default should to just show the most recent logs and as you scroll up, it loads more. If you search, it could bring you to the most recent result with previous/next buttons to cycle through. I am trying to figure out the use case for a time range in the context of logging. Searching could have a specific option to go to a point in time.
• Sounds like this will be fixed so all good there.
• That wasn't quite what I was referring to. I think it kind of requires searching to be changed. Kind of like having what the context tab does, but in the main log window, but imagine all the context windows for all results of your search showing in that main window where the previous/next buttons cycle through them, and you can still just scroll forward or back from each highlighted search matched line. Does that make sense?

[randy-girard]

Also thinking about the live view, does it make sense to have a whole seperate page for that? You could just have a small button at the bottom (or top in signoz current case) to "jump to live logs" if you scroll back in time, and restore live logs when you scroll to current time or something like that.

[nityanandagohain]

• Changing order in live view makes sense. LOGS[Live View]: appned new logs below like taling #7321
• Do you mean this in the context of "context logs" or the normal explorer view ?
• yes
• I couldn't follow, can you give an example ?

Yeah this maybe a good point to solve in future and try to see if we can combine live view in the same logs explorer . cc @GeekBoySupreme

[randy-girard]

• 👍 That would be cool as an option.
• In the normal explorer view. Jumping to the context log seems extraneous if its possible to just have that in the normal view. If I search for something and am interested in a specific result based on the surrounding log lines, I would have to click into every one of them to find it.
• N/A
• Maybe the search is fine, but making a way from the log views (both normal explorer and live) to be able to "goto" the log line in whatever view you are in and showing the context there. I know this is effectively what the context window is doing so maybe I just need to adapt. Just thinking how it might be a little more user friendly. Not sure how much sense this makes. Here is an example that betterstack does when you click on the date, it will basically just reload the logs at the point in time that line is.
  

Another idea could be maybe the live log view being the default?