This epic supersedes previous [Opstrace integration](https://gitlab.com/groups/gitlab-org/-/epics/6976 "Integrate Opstrace with GitLab") and [vision implementation](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/70 "Observability New Vision Implementation Plan") plans. For GitLab self-monitoring, follow this epic: https://gitlab.com/groups/gitlab-org/opstrace/-/epics/120+ If you have any questions or feedback, you can leave a comment in this epic. ## Goal **Observability Group 1-year goal:** * Enable customers to effectively manage and visualize their application and infrastructure performance within GitLab. * Achieve minimal maturity and release the closed beta of Tracing, Metrics, and Logging categories * Our goal aligns with the broader [company objective](https://internal.gitlab.com/handbook/company/yearlies/#fy25-yearlies) to differentiate on platform by successfully delivering new capabilities to market **Read more:** [Direction page](https://about.gitlab.com/direction/analytics/observability/#whats-our-1-year-plan) ## Roadmap With the current team capacity, we aim to release the closed Beta of all categories as well as cloud connector integration by F25-Q3. GA Launch planned for FY26. Breakdown per quarter: <table> <tr> <th> </th> <th> FY24 Q4 (2023-11-01 - 2024-01-31) </th> <th> FY25 Q1 (2024-02-01 - 2024-04-30) </th> <th> FY25 Q2 (2024-05-01 - 2024-07-31) </th> <th> FY25 Q3 (2024-08-01 - 2024-10-31) </th> <th>FY26</th> </tr> <tr> <td> [**Tracing**](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/73 "Tracing FY25") </td> <td> [Beta](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/78 "Tracing to Beta") </td> <td> </td> <td> </td> <td> </td> <td> [GA](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/79 "Tracing to GA") </td> </tr> <tr> <td> [**Metrics**](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/93 "Metrics FY25") </td> <td> [Experiment](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/83 "Metrics to Experiment") </td> <td> [Beta](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/102 "Metrics to Beta") </td> <td> </td> <td> </td> <td> [GA](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/103 "Metrics to GA") </td> </tr> <tr> <td> [**Logging**](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/94 "Logs FY25") </td> <td> </td> <td> [Experiment](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/91 "Logs Experiment") </td> <td> [Beta](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/97 "Logs Beta") </td> <td> </td> <td> [GA](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/98 "Logs GA") </td> </tr> <tr> <td> [**Cloud Connector**](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/95 "Observability - Cloud Connector FY25") </td> <td> </td> <td> </td> <td> [Experiment](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/100 "Observability - Cloud Connector Experiment") </td> <td> [Beta](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/101 "Observability - Cloud Connector Beta") </td> <td> [GA](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/115 "Observability - Cloud Connector GA") </td> </tr> </table> ## Use Cases Focusing on these primary use cases for Beta: - Triage alert and respond to incidents (On-call engineers: Dev & Ops/SRE) - Track deployment, debug and optimize applications (Developers) ## High-level requirements * SaaS-only * A Cloud Connector integration will enable Self-Management customers store observability data on a cloud-based storage * Use [OpenTelemetry](https://opentelemetry.io/) as the instrumentation standard for collecting telemetry data * Use ClickHouse Cloud as Data store * Client-side sampling only * Data can be access at the project-level only (no group-level federation/aggregation) * No integration work * Users will leverage existing 3rd party integrations based on OpenTelemetry to integrate with their application, infrastructure or off-the-shelf software - if it exists for their technology. * Users will use the API to build custom integration for non supported tools or custom-built software. * Usage tracking * Should leverage current storage quota UI * Auto-alert on limit attainment * Licensing / Entitlement / Quota / Billing * At minimum for GA features will be available to Ultimate customers with a storage limit. * Additional requirements will depend of the decided strategy and may be implemented after initial GA. ## Detailed requirements GA requirements (previously in this in [this spreadsheet](https://docs.google.com/spreadsheets/d/1ri7MXkcX9PwNAZXmPIMngMcZmXu7tYt6_X-5DUadSBU/edit#gid=659177685)) are detailed in sub-epics per release (ie. Traces to Beta, Traces to GA, etc.). The [Post-GA](https://gitlab.com/groups/gitlab-org/opstrace/-/epics/99 "Observability - Post-GA") epic will contain work considered out of scope from these requirements and prioritized after delivery of GA work items. Notes: * These requirements captures the minimal - yet ambitious - scope based on previous discussions. * They don't aim to be exhaustive. For example, defining scalability requirements or design expectations will be an ongoing process for each category as we move towards GA, taking into account what’s feasible or not given the timeline and team capacity.