Monitor:Logging Deprecation

Deprecation Summary

Summary of the feature that is being deprecated:

We previously launched a solution that enabled users to easily install the ELK stack to aggregate and manage their application logs. GitLab users could directly search for relevant logs in the GitLab UI.

However, since we deprecated GitLab’s certificate-based integration with Kubernetes clusters, GitLab Managed Apps is also deprecated. Since the ELK stack was a GitLab Managed app, we currently don’t have a recommended solution for Logging within GitLab.

Documentation:

• Aggregate and store logs
• Kubernetes Logs (DEPRECATED)

Proposal

• %14.7 documentation changes are made to reflect features that are being deprecated, !77419 (merged)
• %14.7 Deprecation MR, !77422 (merged)
• %14.8 in-product shows the features that are being deprecated, #350601 (closed)
• %14.8 Deprecation message added to the CHANGELOG.md file
• %14.10 Technical Breakdown for feature removal, Technical Breakdown for Monitor: Logging Removal (gitlab-org/monitor/respond#111 - closed)
• %15.0 Removal MR, Removal MR for Logging (!79764 - merged)
• %15.0 Disabled logging with feature flag, #360182 (closed)
• %15.2+ Deprecated code deleted as team has availability
  • Logging: Delete UI code for viewing pod logs (#360188 - closed)
  • Logging: Delete UI code for configuring logging... (#360190 - closed)
  • Logging: Delete backend code for viewing pod logs (#360193 - closed)
  • Logging: Deprecate usage metrics for ElasticSta... (#360195 - closed)
  • Logging: Delete backend code for configuring lo... (#360192 - closed)
  • Logging: Cleanup database of `clusters_applicat... (#360196 - 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

Is this a breaking change or not? If so, please add instructions for how users can update their workflow. TBD

Affected Topology

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

Affected Tier

This feature available in GitLab Core / All Tiers

Checklist

• This issue/epic is shared with the team at a team meeting for grouprespond
• @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.
• Post the announcement of this deprecation in the following Slack Channels:
  • #ops-section
  • #product

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