Consistent timeouts on Trace Hierarchy view #2321
-
For a bit of prior context, we've upgraded from 2023.3 to 2024.x, with the intent of utilizing the new trace capabilities in Seq This is where it is occurring for a more visual representation of this issue. We process a lot of logs, I've been quoted upwards of 80gb a day are incoming. We've spent quite a bit of time digging from our side from which we've checked
What we've noticed from debugging is that the query used for the graph doesn't seem to be time-gated by the timeframe selected by the user?
By adding a timeframe of 1hr to the above query we're able to bring it to under 4 seconds. We also tried changing the 'Default to search last' query time to 15 minutes and trying to load the view again, this didn't seem to make a difference. Do you guys have any idea how we can fix this issue? EDIT: We believe that some of this might be due to indexing, It has been about 24 hours since we upgraded. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi Tyler, thanks for your message. The Data > Storage screen will show whether your indexes are up-to-date or not; it sounds like you might have a lot of historical data from pre-2024.3 that will need to be indexed before trace id searches will work. Let me know how you go, and if things don't seem to be moving forward please drop us a line via Greetings from another BNE dev! 😎 Nick |
Beta Was this translation helpful? Give feedback.
Hi Tyler, thanks for your message. The Data > Storage screen will show whether your indexes are up-to-date or not; it sounds like you might have a lot of historical data from pre-2024.3 that will need to be indexed before trace id searches will work.
Let me know how you go, and if things don't seem to be moving forward please drop us a line via
[email protected]
with some more information about the system.Greetings from another BNE dev! 😎
Nick