Remove Provisioned ObservabilityContainer from Observability pages
What does this MR do and why?
We are removing ProvisionedObservabilityContainer
from all Observability pages. The component was required to enable API calls towards external Observability endpoints and handling the authentication and provisioning flow.
With the new API version v4
those API calls are proxied through Rails, so there is no need for that anymore ( See !131577 (merged) for architectural changes )
Close Remove observability provisioning container in ... (gitlab-org/opstrace/opstrace#2768 - closed) and Change API routes in GitLab UI apiConf to use n... (gitlab-org/opstrace/opstrace#2767 - closed)
Changes:
- Update Observability API URLs to internal endpoints
- Remove ProvisionedObservabilityContainer wrapper
- Build
observabilityClient
directly in the page roots - Remove checks for
isObservabilityEnabled
as that is not needed anymore
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
NA
How to set up and validate locally
Testing this change requires setting up a virtual machine through https://gitlab.com/gitlab-org/opstrace/devvm