-
Notifications
You must be signed in to change notification settings - Fork 4.1k
log: add consistent tagging of failed assertions that are alertworthy #102041
Copy link
Copy link
Closed
Labels
A-observability-infC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)O-postmortemOriginated from a Postmortem action item.Originated from a Postmortem action item.db-cy-23
Description
Sometimes in production we have situations that don't rise to the level of panic (programmer error) or Fatalf (node should crash) but still want to alert the operator that something serious is going on that requires immediate attention. This cannot be simply codified into an ERROR severity log since not all ERROR level lines rise to the level of requiring operator involvement.
This ticket tracks consistent messaging for these types of errors so that they can be alerted upon easily. This can be done either through a log tag, or through some pre-set formatting structure in the error message.
Jira issue: CRDB-27233
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-observability-infC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)O-postmortemOriginated from a Postmortem action item.Originated from a Postmortem action item.db-cy-23