Database State: Customer Signal Collections
This epic collects customer signals related to database state issues. Each sub-issue represents a distinct pattern or problem observed in the field. The goal is to gather enough signal before committing to engineering work.
## How to add a new signal topic
> **Audience:** GitLab Support and Database Health team members.
**First, check whether an existing sub-issue already covers the topic.** If it does, add your reference as a comment there instead of creating a new issue.
**Do not create a new sub-issue unless you already have at least 2 references** (RFH issues or Zendesk tickets) in hand. If you only have one signal, hold off until you find a second before opening anything.
When you have 2 or more references ready:
1. Create a new issue in `gitlab-org/gitlab` using the template below as the description.
2. Set this epic ([&21682](https://gitlab.com/groups/gitlab-org/-/work_items/21682)) as the parent.
3. Add each reference as a **comment** on the new issue immediately after creating it (see format in the template).
### Privacy reminder
These issues are **not confidential**, so never include customer-identifying information — no customer names, company names, or any other details that could identify a specific customer. See the [SAFE framework](https://handbook.gitlab.com/handbook/legal/safe-framework/) for guidance. Version numbers and general configuration details are fine.
---
### New signal issue template
Use the following as the description when creating a new sub-issue:
````markdown
> [!NOTE]
> This is a collection issue. It is used to gather customer signals (RFH issues, Zendesk tickets)
> that will inform database state work. See the parent epic for instructions on adding a new signal topic.
> [!WARNING]
> **Privacy:** These issues are not confidential. Do not include any customer-identifying information —
> no customer names, company names, or details that could identify a specific customer.
> See the [SAFE framework](https://handbook.gitlab.com/handbook/legal/safe-framework/) for guidance.
> Version numbers and general configuration details are fine.
## Background
<!-- Describe the database state pattern or problem observed in the field.
Include relevant technical details such as version numbers or configuration,
but do not include any customer-specific information. -->
## Contributing References
Add references as **comments** on this issue, not inline here. Each comment should include:
1. A 1–3 sentence summary of the customer problem, written without any customer-identifying information.
2. The link to the RFH issue or Zendesk ticket.
Links should be to an RFH issue, Zendesk ticket, or GitLab bug issue. If your reference doesn't
fit the signal described here, check the [parent epic](https://gitlab.com/groups/gitlab-org/-/work_items/21682)
for instructions on adding a new signal topic.
**This issue should have at least 2 references before it is considered active.**
````
epic