datalust
Trace view only shows log entries ticks when they are not filtered out
This might be by design, but I found it very strange to see.
When I'm looking for traces, I usually look for specifc log lines. For example I use a filter to only see the log lines with "End summarizing recording" to find all completed summaries. When I do that, and I open the Trace view for one of the items I found, you only see the tick mark for the last log line that is part of this trace (because that is the only line visible in the results due to my filter). I do see the trace information for all others, but there is no tick that I can hover to see the message of the corresponding log line.
This is how it looks filtered:
But when I loose the filter, and then have to scroll through a lot of loglines to find the same item I see this:
Even when I filter based on datetime to just have the last 2 loglines remaining )so we don't see the others as well) I still get all the ticks. It's only when filtering on the text field as in the first screenshot where you only see the last tick mark.
It's not really a big issue, but I don't understand why this is happening. In this example it can be really handy to be able to hover over those tick marks and see the message, the first tick mark is "Begin summarizing...." by the way
Is this by design, or could these tick marks be included for the entire trace regardless of whether loglines are filtered out!
Thanks for the report @jbennink :+1:
The behaviour here is a bit surprising. The trace view largely operates outside of the normal date range and filtering, because you can't really render half a trace. Log events, wherever they appear, are always bounded by the filter and date range. It looks like you might actually be exercising a bug there. If you refresh the page with your narrower date range, do you still see all the ticks in the trace bar? Or just the 2 that match?
I redid the filter just now and with just two log lines showing, the bottom one having a trace, I choose Show Trace and saw this:
So it is just shoing the one trace visible in the log lines that are filtered. So the tick marks are only shown for the log line that abide by the filtered and daterange it seems. That tick mark is part of the last POST line.
After enlaring the daterange to include more log line I also see the other tick marks.
Once I add the filter so I only get 1 of the log lines, it only shows me the one tick mark for the remaining trace?
But only after closing the trace view and freshing. At first I just changed the filter, while having the trace view open and then It did not update the view to only show 1 tick mark. But after collapsing the trace view, pressing refresh just to be sure and reopening the trace view I did end up with only 1 tick mark.
P.S> When the trace view was open before and I changed to from date to include more the trace view did refresh and immediatelly showed me all tick marks as shown in the second screenshot.
Hi @jbennink
Thanks for the update. The design (right or wrong) of the trace view is to show the logs that match the current context (time range, filters, signals). The bug is that the trace view is only updated with new log events. When log events leave the context they are not removed from the visualization.
Hi @jbennink - I think the intention of Liam's comment above:
The bug is that the trace view is only updated with new log events. When log events leave the context they are not removed from the visualization.
is that we'll make changes to improve this scenario.
