Database Group Triage for week ending 2023-12-01

About

This issue is used by groupdatabase to triage issues and make sure they get properly assigned and prioritized. Each week, a bot will look up the old issue, pick the next assignee in the list, and submit a new issue with a list of any issues that may need attention from the team.

Last week's issue

Process

• Review any issues with undefined types
• Post any questions or pressing issues to the database group meeting doc
• Post a comment on the database group status issue

  For triage this week there were 0 issues in need of triage, 5 issues without throughput labels, and 11 other database issues reviewed. <link to this issue>

Bugs needing Severity

For each issue below:

1. For each typebug, spend up to 1 hour investigating or fixing the issue.
2. Assign it one of severity1, severity2, severity3, or severity4
3. Document any findings you make in a comment on the issue, and if the issue still needs additional work or refinement, consider looping in @alexives and @rogerwoo to help with scheduling and priority.

• 16.5.2 to 16.6.0 db migration problem

Issues with Undefined Type

For each issue below:

1. Assess if the issue is appropriately assigned to groupdatabase, if not add the correct group label.
2. Add the proper work type label, or if the issue is a request for support, redirect the user to our support resources with the following message:

   Hey @author. Based on the information given, this request for support is out of the scope of the issue tracker (which is for new bug reports and feature proposals). Unfortunately, I won't be able to help get it resolved. However, for support requests we have several resources that you can use to find help and support from the Community, including:
   * [Technical Support for Paid Tiers](https://about.gitlab.com/support/)
   * [Community Forum](https://forum.gitlab.com/)
   * [Reference Documents and Videos](https://about.gitlab.com/get-help/#references)
   
   Please refer to our [Support page](https://about.gitlab.com/support/) for more information.
   
   If you believe this was closed in error, please feel free to re-open the issue.
   
   /label ~"support request"
   /close

3. If the issue needs further investigation, add databasetriage and spend up to 1 hour of investigating the issue.
4. Document any findings you make in a comment on the issue, and if the issue still needs additional work or refinement, consider looping in @alexives and @rogerwoo to help with scheduling and priority.

• Database Status Summary (Week ending - 2023-12-02)
• Validate merge request url
• Patroni cause alerts for all patroni services
• Isolate GitLab database schema migration helpers code into "gitlab-database-schema_migrations" gem
• Define alerts for the batched background migration framework

Recent issues labeled database

For each issue below:

1. If the issue has no group label, consider if it should be addressed by groupdatabase and if so label it.
2. If the issue has a group, and you think they may need assistance from us:
   • If the issue needs further investigation, add databasetriage and spend up to 1 hour of investigating the issue.
   • Document any findings you make in a comment on the issue, and if the issue still needs additional work or refinement, consider looping in @alexives and/or @rogerwoo

• groupknowledge Follow-up from "Fix bug with pages_deployments files not being deleted on disk"
• groupsource code Add FE components for group-level MR approval rules
• groupthreat insights Apply limit for group.vulnerabilitySeveritiesCount GraphQL API
• groupknowledge Files in pages_deployments are not deleted on disk when deactivated_pages_deployments_delete_cron_worker runs
• groupcompliance Drop unique index from namespace_id field for audit_events_streaming_http_group_namespace_filters
• groupthreat insights Implement filtering of vulnerabilities with identifier, location, assignee, branch, SLA, date detected on the vulnerabilities GraphQL query
• groupthreat insights Provide text search capabilities to the GraphQL Vulnerabilities Query
• groupthreat insights Background migration to backfill ts_vector lexeme columns on Vulnerability::Reads
• groupthreat insights Implement ts_vector lexeme colums on Vulnerability::Reads to support Full Text Search in postgres
• groupthreat insights Migrate Vulnerability::Reads to new partitioning
• groupthreat insights Implement initial Vulnerability::Reads partitioning strategy

Customer Issue Hand-offs

For each issue below:

1. If the item already has a back and forth, check in with the @praba.m7n to see if what needs to be handed off
2. Consider if it's right for our team and if not, ask the support rep to follow up with the correct team.
3. If the item is right for our team, spend some time accessing it and trying to assist.
4. If you need help, and the request seems pressing, ask in the team channel if there's someone who can help dig into it.

• GitLab 15.11 DB migration workaround is not working for customer~"Help group::Database"

Review Recent Postgres Checkup

For each database:

1. Are there new queries in the top queries (See: K003 Top-15 Queries by total_time) compared to a previous report?
2. If there are new queries, Spend up to 30 minutes trying to understand their sources
3. If there are new queries, file an issue and assign to the team that owns the query, or if unable to source, then the team that owns the table
4. If there are no new queries, review the top 5 queries for each to see if there are already investigations, or file issues to investigate them

• Review recent Primary Checkup for new Top Queries
• Review recent CI Checkup for new Top Queries

@alexives if @stomlinson isn't available this week, please reassign to @dfrazao-gitlab cc @rogerwoo