4 ms·
I love the idea of capturing all events and providing the user with an option to label "useful" events. Similarly, I'd like to capture API calls. In a typical m
by eclipsetheworld 7y ago
I love the idea of capturing all events and providing the user with an option to label "useful" events. Similarly, I'd like to capture API calls. In a typical modern SPA + REST api setup, calls to the REST api often correspond to events. An analytics integrations that captures all api calls and provides tools to label/transform these api calls as events would prove similarly useful.
- james_impliu 7y agoWe were debating applying it at a framework or query level but were nervous about this being harder to "clean up" conceptually - what would the equivalent of the "PostHog UX toolbar" need to look like to make that possible do you think?
- eclipsetheworld 7y agoApi calls could be treated as events. Furthermore, match groups should be more powerful allowing any query of the form [field] [operator] [value] (e.g. Text equals {value} or URL contains "/checkout"). However, the challenges that come to my mind are: - (i) How to handle the request/response being essentially two events - Should they be merged into one event? - (ii) How to handle request/response bodies and http headers? - Passing the bodies as event properties does not seems intuitive and it would be valuable to query them with XPath / JSONPath. - Http headers could be passed as event properties