## Goal Address known scalability problems with Error Tracking by migrating the datastore to Clickhouse Focusing on [SaaS first](https://about.gitlab.com/handbook/product/product-principles/#sts=SaaS%20First), we expect initial development work for that effort to include following: 1. Connecting Rails to Clickhouse 1. Enabling Clickhouse in GDK 1. Refactoring Error tracking to utilize Clickhouse ([as proposed here](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/82620)) ## Iterations ### Iteration 1, ending April 22 - [Evaluate which ClickHouse gem to use](https://gitlab.com/gitlab-org/gitlab/-/issues/358158) :white_check_mark: - [Investigate query performance with ClickHouse](https://gitlab.com/gitlab-org/gitlab/-/issues/358105) :white_check_mark: - [Investigate Clickhouse HTTP interface](https://gitlab.com/gitlab-org/gitlab/-/issues/357883) :white_check_mark: ### Iteration 2, ending May 6 - [Experiment: DB schema for Error Tracking](https://gitlab.com/gitlab-org/gitlab/-/issues/358396) :white_check_mark: - [Validate schema design with ClickHouse, Inc. consultants](https://gitlab.com/gitlab-org/gitlab/-/issues/357937) :white_check_mark: - [Create Error Tracking schema in Clickhouse](https://gitlab.com/gitlab-org/gitlab/-/issues/357472) :white_check_mark: - [Data access layer interface for Error Tracking](https://gitlab.com/gitlab-org/gitlab/-/issues/359843) :white_check_mark: ### Iteration 3, ending May 20 - [Implement Error Tracking with ClickHouse](https://gitlab.com/gitlab-org/gitlab/-/issues/361341) :white_check_mark: ### Iteration 4, ending June 3 - [Define application limits for error tracking](https://gitlab.com/gitlab-org/gitlab/-/issues/358392) :white_check_mark: ### Iteration 5, ending June 18 - [Investigate data cleanup strategies](https://gitlab.com/gitlab-org/gitlab/-/issues/358267)