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.

Sign up for GitHub

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

Jump to bottom

*: new logging channels OPS and HEALTH #57171

Merged
merged 3 commits into from
Dec 16, 2020
Merged

*: new logging channels OPS and HEALTH #57171

merged 3 commits into from
Dec 16, 2020

Commits on Dec 16, 2020

  1. *: new logging channels OPS and HEALTH 

    Release note (cli change): 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 the channel 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-, down-replication; range unavailability.
    @knz
    knz committed Dec 16, 2020
    Configuration menu
    Copy the full SHA
    4f0d140 View commit details
    Browse the repository at this point in the history

  2. util/log: report non-OPS fatal calls on the OPS channel 

    Release note (cli change): Server terminations that are triggered when
a node encounters an internal fatal error are now reported on the OPS
channel. The exact text of the error is not reported on the OPS
channel however, as it may be complex (e.g. when there is a replica
inconsistency) and the OPS channels is typically monitored by tools
that just detect irregularities. The text of the message refers
instead to the channel where the additional details can be found.
    @knz
    knz committed Dec 16, 2020
    Configuration menu
    Copy the full SHA
    0ab9fbe View commit details
    Browse the repository at this point in the history

  3. util/log: file zone config changes towards the OPS channel 

    Zone config changes interest the DBAs of the cluster as a whole more
than they interest the DBA of the individual SQL application.

Release note (cli change): The notable events `set_zone_config` and
`remove_zone_config` are now sent to the OPS channel.
    @knz
    knz committed Dec 16, 2020
    Configuration menu
    Copy the full SHA
    3a65664 View commit details
    Browse the repository at this point in the history