Monitor: Tracing Deprecation

Deprecation Summary

Summary of the feature that is being deprecated:

We previously launched a tracing solution that allows users insight into the performance of a deployed deployed application, tracking each function or microservice that handles a given request using Jaeger. Jaeger is an open source, end-to-end distributed tracing system.

However, since the acquisition of OpsTrace we will be deprecating these features in %15.0. GitLab Tracing will be replaced by a new offering once OpsTrace has been integrated with GitLab.

Documentation:

• Tracing

Proposal

• %14.7 documentation changes are made to reflect features that are being deprecated, !77391 (merged)
• %14.7 Deprecation MR, !77421 (merged)
• %14.8 in-product shows the features that are being deprecated, #350601 (closed)
• %14.8 Deprecation message added to the CHANGELOG.md file - won't do - #346540 (comment 897897461)
• %14.10 Technical Breakdown for feature removal, Technical Breakdown for Monitor: Tracing Removal (gitlab-org/monitor/respond#110 - closed)
• %15.0 Removal MR, Removal MR for Tracing (!79765 - merged)
• %15.0 Disabled tracing with feature flag, #359904 (closed)
• %15.2+ Deprecated code deleted as team has availability
  • Tracing: Deprecate usage ping & snowplow metrics (#359906 - closed)
  • Tracing: Remove UI at Monitor > Tracing and lef... (#351387 - closed)
  • Tracing: Remove UI at Settings > Monitor > Trac... (#351388 - closed)
  • Tracing: Remove backend application code (#359907 - closed)
  • Tracing: Cleanup database of project_tracing_se... (#359909 - closed)

Here is a link to the Deprecations, removals, and breaking changes process.

Note: A deprecation needs to have an initial announcement in the release post notifying the community at least two releases in advance of the date of planned removal. Deprecations should also be included in the documentation for at least 2 releases prior to the final removal.

Breaking Change

TBD

Affected Topology

This deprecation is for both Self-managed and SaaS users.

Affected Tier

This feature available in GitLab Core / All Tiers

Checklist

• @mention your stage's stable counterparts on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.

  • To see who the stable counterparts are for a product team visit product categories
    • If there is no stable counterpart listed for Sales/CS please mention @timtams
    • If there is no stable counterpart listed for Support please @mention @gitlab-com/support/managers
    • If there is no stable counterpart listed for Marketing please mention @williamchia

• @mention your GPM so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.

Deprecation Milestone

In which milestone will this deprecation be announced? %14.8

Planned Removal Milestone

In which milestone will the feature or functionality be removed and announced? %15.0

Links