<!-- Use this template as a starting point for deprecations. --> ### Deprecation Summary <!-- This should contain a brief description of the feature or functionality that is deprecated. The description should clearly state the potential impact of the deprecation to end users. It is recommended that you link to the documentation. The description of the deprecation should state what actions the user should take to rectify the behavior. If the deprecation is scheduled for an upcoming release, the content should remain in the deprecations documentation page until it has been completed. For example, if a deprecation is announced in 14.9 and scheduled to be completed in 15.0, the same content would be included in the documentation for 14.9, 14.10, and 15.0. --> **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](https://gitlab.com/groups/gitlab-org/-/epics/6976). **Documentation:** - [Tracing](https://docs.gitlab.com/ee/operations/tracing.html#tracing) ### Proposal - [x] %"14.7" documentation changes are made to reflect features that are being deprecated, https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77391 - [x] %"14.7" Deprecation MR, https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77421 - [x] %"14.8" in-product shows the features that are being deprecated, https://gitlab.com/gitlab-org/gitlab/-/issues/350601 - [ ] ~~%"14.8" Deprecation message added to the `CHANGELOG.md` file~~ - won't do - https://gitlab.com/gitlab-org/gitlab/-/issues/346540#note_897897461 - [x] %"14.10" Technical Breakdown for feature removal, https://gitlab.com/gitlab-org/monitor/respond/-/issues/110+ - [x] %"15.0" Removal MR, https://gitlab.com/gitlab-org/gitlab/-/merge_requests/79765+ - [x] %"15.0" Disabled tracing with feature flag, https://gitlab.com/gitlab-org/gitlab/-/issues/359904 - [ ] %"15.2"+ Deprecated code deleted as team has availability - https://gitlab.com/gitlab-org/gitlab/-/issues/359906+ - https://gitlab.com/gitlab-org/gitlab/-/issues/351387+ - https://gitlab.com/gitlab-org/gitlab/-/issues/351388+ - https://gitlab.com/gitlab-org/gitlab/-/issues/359907+ - https://gitlab.com/gitlab-org/gitlab/-/issues/359909+ Here is a link to the [Deprecations, removals, and breaking changes](https://about.gitlab.com/handbook/marketing/blog/release-posts/#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 <!-- Is this a breaking change or not? If so, please add instructions for how users can update their workflow. --> **TBD** ### Affected Topology <!-- Who is affected by this deprecation, Self-managed users, SaaS users, or both? This is especially important when nearing the annual major release where breaking changes and removals are typically introduced. These changes might be seen on GitLab.com before the official release date. --> This deprecation is for both Self-managed and SaaS users. ### Affected Tier <!-- Which tier is this feature available in? * Free * Premium * Ultimate --> 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](https://about.gitlab.com/handbook/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 ? --> 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? --> In which milestone will the feature or functionality be removed and announced? %"15.0" ### Links <!-- Add links to any relevant documentation or code that will provide additional details or clarity regarding the planned change. Also, include a link to the removal issue if relevant. -->