<!-- 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:** GitLab self-monitoring is meant to enable self-hosted GitLab administrators with the tools to operate GitLab. Self-monitoring will be deprecated in %"14.9" and removed in %"15.0". The self-monitor project shares code with the Metrics dashboard, which will be deprecated in %"15.0". Removing this does not mean people can no longer self-monitor. But they will need to wire things up themselves to monitor their GitLab instance. It is recommended that self-hosted users monitor their GitLab instance with alternative observability tools like Prometheus, Grafana, etc. Note: Initially GitLab self-monitoring was going to be deprecated, but not removed. i.e. GitLab self-monitoring was no longer supported. Due to the dependencies on GitLab Metrics, which will be removed in %"15.0", it was decided that GitLab self-monitoring will also be removed. **Documentation:** - [Self Monitoring](https://docs.gitlab.com/ee/administration/monitoring/gitlab_self_monitoring_project/) ### Proposal - [x] %"14.7" remove the Self-Monitoring category, https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/96817 - [x] %"14.9" documentation changes are made to reflect features that are being deprecated, https://gitlab.com/gitlab-org/gitlab/-/merge_requests/81923+ - [x] %"14.9" create a deprecation entry, https://gitlab.com/gitlab-org/gitlab/-/merge_requests/81921+ - [x] %"15.10" in-product shows the features that are being deprecated, https://gitlab.com/gitlab-org/gitlab/-/issues/353145+ - [ ] %"15.9" Deprecation message added to the `CHANGELOG.md` file: https://gitlab.com/gitlab-org/gitlab/merge_requests/XXX - [ ] %"15.10" Technical Breakdown for feature removal, https://gitlab.com/gitlab-org/monitor/respond/-/issues/112+ - [ ] %"16.0" Removal MR - [ ] %"16.0" Deprecated code removed in %"16.0": MR (consider removing code in multiple phases/MRs) - UI removal (required for %"16.0") - API removal (required for %"16.0") - Backend removal (can be done in future milestones if necessary) 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. Yes ### 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 users. ### Affected Tier This feature available in gitlab~13116818 / All Tiers ### Checklist - [ ] This issue/epic is shared with the team at a team meeting for gitlab~10690732 - [ ] @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. - [ ] 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.9" ### Planned Removal Milestone %"15.0"