Spike: Define technical architecture and plan for the proposed Jitsu replacement
Release notes
Problem to solve
See the parent epic description for overall context.
We have a high-level architecture and direction defined for what a potential Jitsu replacement could look like in our Product Analytics stack in the parent epic description. However, this is a rough idea and not fully defined or scoped.
Proposal
Further define the proposal in the epic description. Create child epics & issues as needed to describe the work to be done. Provide rough size estimates of what each piece would take to complete.
Once we have a plan with rough sizing, we can then balance the cost of building our own collector compared to continuing to use Jitsu and make a decision on which direction to go in the future.
Intended users
Feature Usage Metrics
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.