Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

*: new logging channels OPS and HEALTH #9536

Closed
jseldess opened this issue Jan 29, 2021 · 1 comment
Closed

*: new logging channels OPS and HEALTH #9536

jseldess opened this issue Jan 29, 2021 · 1 comment
Assignees
Milestone

Comments

@jseldess
Copy link
Contributor

PR: cockroachdb/cockroach#57171

  • Logging events that are relevant to cluster operators are now categorized under the new OPS and HEALTH logging channels. These can now be redirected separately from other logging events.
    • The OPS channel is used to report "point" operational events, initiated by user operators or automation:
      • Operator or system actions on server processes: process starts, stops, shutdowns, crashes (if they can be logged), including each time: command-line parameters, current version being run
      • Actions that impact the topology of a cluster: node additions, removals, decommissions, etc.
      • Cluster setting changes
      • Zone configuration changes.
    • The HEALTH channel is the channel used to report "background" operational events, initiated by CockroachDB or reporting on automatic processes:
      • Current resource usage, including critical resource usage
      • Node-node connection events, including connection errors and gossip details
      • Range and table leasing events
      • Up- and down-replication, range unavailability [#57171][#57171]
@taroface
Copy link
Contributor

Closed by #10273.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants