Horde chokes up when analytics try’s to pull too much data, the TopN field filters code was commented out.
Steps to Reproduce
Hello,
For dealing with metrics that will have many entries (e.g. LLM telemetry) the TopN seems like the right filter to apply so that the view remains responsive and reasonable in the horde analytics dashboard. It looks like the top N filter was commented out in the CL below. Is there a reason for this? is there a better way to limit how much data the analytics dashboard try’s to pull and display?
Horde: Do not filter to top/bottom for prod deployment
#okforgithub public
#submittool bypass
#rnx
#ROBOMERGE-AUTHOR: josh.engebretson
#ROBOMERGE-SOURCE: CL 38593665
#ROBOMERGE-BOT: (v1212-38496376)
#robomerge[bot5] -FNMain
Hello, I’ve looked into this, and while CL 38593665 comments out the functionality, the ticket that added the TopN and BottomN functionality to Horde Analytics in the first place (UE-230085 via CL 38181517) is still open.
This could mean that the implementation was not finalized or meant for release. I’ve reached out to the owner for an update and thoughts on a better way to limit how much data the analytics dashboard pulls.
They’re currently on leave, but are returning this week, and I’ll get that information to you as soon as possible.
Hello, I’ve spoken with the team, and this is unfortunately a feature that we would like to include with Analytics, but we don’t currently have a timeline for fixing up.
On limiting the data in the dashboard, this is going to require collapsing some of the data down using the GroupBy field in the metric config, though the practicalities of this would depend on the data that you’re ingesting.
No problem! I saw it in the default config and just the code commented out so wanted to reach out. Our use was similar to the example one. Report the top X resources for memory. We’ll use other options better suited for ingesting and displaying large data in the mean time. Looking forward to seeing the PRS work stood up and built in to horde. Thanks!