Keep secrets out of support details
A connection URI can contain usernames, passwords, host information, and database names. Treat its full value like a credential: do not paste it into a public issue, screenshot, chat, or unfiltered log. If support needs to recognize the target, provide a redacted form that preserves only the database type and non-sensitive context.
Error output may also reveal query text, table names, or customer data. Review it before sharing and replace private values with examples that preserve the same structure. Avoid attaching a full environment file when a short, sanitized excerpt can explain the setup.
Include details that help isolate the failure
Record which action failed, whether it was connection setup or a later query, the approximate time, and whether the problem repeats. Include the database type and a non-secret connection label if available. These details help distinguish authentication, permission, naming, and network problems without disclosing access.
Mention recent changes such as credential rotation or a database rename and the safe checks already performed. Never send a password to prove it works. If a secret may have been exposed, rotate it through the normal process and update the saved connection before retrying.