Skip to content

Use new tracing backend suggested by Observability team

Reuben Pereira requested to merge rp/use-new-tracing-backend into master

What does this MR do and why?

Describe in detail what your merge request does and why.

Content

  • Use new tracing backend suggested by Observability team

The Observability team is phasing out the Jaeger UI. This MR changes the destination URL that we upload traces to.

When this MR is merged, a new token is required for GITLAB_O11Y_NAMESPACE_TOKEN since the previous one (https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/19488) was for the https://gitlab.com/gitlab-com/gl-infra group. The new one needs to be for the gitlab-org/release-tools> project.

I've opened https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/20070 for the new token. I'll install the new token in the CI/CD variable once this MR is merged.

See gitlab-org/opstrace/opstrace#2427 (closed).

Testing

I've tested uploading traces using the new URL. It worked, and here's the uploaded trace: https://gitlab.com/gitlab-org/release-tools/-/tracing/c8cce3e7-bb32-e032-2818-d755e9eb961b.

GITLAB_O11Y_URL='https://observe.gitlab.com/v3/9970/430285/ingest/traces' GITLAB_O11Y_NAMESPACE_TOKEN='glpat-' RELEASE_BOT_DEV_TOKEN='glpat-' RELEASE_BOT_OPS_TOKEN='glpat-' RELEASE_BOT_PRODUCTION_TOKEN='glpat-' bundle exec rake 'trace:pipeline_url[https://ops.gitlab.net/gitlab-org/release/tools/-/pipelines/2939306,deployment pipelines]'

Author Check-list

  • Has documentation been updated?
Edited by Reuben Pereira

Merge request reports