Draft: Refactor Tracing Provisioning UI
What does this MR do and why?
- Rename Observability Client Provisioning API to be more generic (
enableTraces
->enableObservability
) - Remove provisioning logic and UI from TracingList. This is extracted in a reusable component
- Add reusable ProvisionedObservabilityContainer
- Handles the provisioning logic and UI, so that each component that is wrapped in the
ProvisionedObservabilityContainer
does not need to handle the provisioning logic and UI itself. This is useful as we are introducing a new Observability Metrics feature and we will need to show the same Provisioning UI used for Tracing. - Made Provisioning UI more generic so that it can be reused for all Observability features.
Prerequisite for metrics: Add Provisioning UI (gitlab-org/opstrace/opstrace#2437 - closed)
Screenshots or screen recordings
Before | After |
---|---|
How to set up and validate locally
-
In rails console enable the experiment fully
Feature.enable(:observability_tracing)
-
Visit tracing https://local.gitlab.com:3443/flightjs/Flight/-/tracing
-
Check the Provisioning UI
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Daniele Rossetti