Skip to content

Removal - Rails Error Tracking UI

For guidance on the overall deprecations, removals and breaking changes workflow, please visit Breaking changes, deprecations, and removing features

Deprecation Summary

The Error Tracking UI will be deprecated in favor of a UI built within the GitLab Observability UI. During this transition, we are also migrating from a per-cluster deployment model for GitLab Observability Backend to a per-tenant deployment model. Because the feature is in Beta, we will not be migrating any existing error data.

Breaking Change

This is a breaking change. Users are encouraged to adopt the replacement capability via GOUI when it becomes available. This is essentially a removal.

Affected Topology

Only SaaS users are affected by this deprecation as integrated error tracking is only available in SaaS

Affected Tier

Free

Checklists

Labels

  • This issue is labeled deprecation, and with the relevant ~devops::, ~group::, and ~Category: labels.
  • This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

Timeline

Please add links to the relevant merge requests.

  • As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0 – 14.8 is the third milestone preceding the major release):
  • On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post.
  • On the major milestone:

Mentions

  • Your stage's stable counterparts have been @mentioned 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 @cfoster3
  • Your GPM has been @mentioned 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

15.9

Planned Removal Milestone

16.0

Links

Edited by Kevin Chu