![]() ![]() dashboard items refreshing logic as well. ![]() This should significantly simplify e.g.In frontend this kind of has already materialized with the insightsLogic, in the backend kind of with the cache refreshes stuff, all excepting.Rather than have N different endpoints for each, we should have a single endpoint to accept the filter object that does multiple dispatch down a chain. ![]() Only given a filter and a result set it should always be possible to both uniquely query + render results.This includes second-order queries like correlation analysis. Insights should be uniquely defined by the "filter" object in both the FE and backend.See below how I'd fit it into the architecture though Note that this covers everything here except session recordings - I think session recordings need fundamentally to have a different system from other insights.I'd define an "insight" as a "time-series metrics query result". Cost of getting this wrong is huge as killing misfeatures is larger than not having them.īelow I'll assume there's a legit use-case:. ![]() I'd go deep to understand the need for "person modal in dashboard" and "session recordings" since they sound like we might not understand the proper problem being solved.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |