[SERVER-75354] Investigate codebase for log line attribute uniformity for databasename Created: 27/Mar/23 Updated: 04/Oct/23 Resolved: 04/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathis Bessa | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Serverless
|
||||||||
| Participants: | |||||||||
| Description |
|
The codebase is logging a DatabaseName with different attribute names such as `db` which is the correct one, `dbName` or `database`. Potentially more. As part of We should investigate places that are using a different attribute name (i.e. not using `db` as an attribute of DatabaseName in logging) and see if they can be changed from whatever attribute they are using, with `db` (by using `logAttrs()`). As a reminder, downstream systems might be looking at log message / error / warning messages. Replacing a log line might in fact cause some issues which is why we need to investigate what can be changed. |
| Comments |
| Comment by Didier Nadeau [ 04/Oct/23 ] |
|
Further discussions led us to realise we can't change the existing lines because any downstream consumer (clients, etc) can rely on them and we can't survey all of these use-cases. |