Operator Logging
The Operator emits logs on the pod console. Logs are structured as JSON for simple machine parsing, however schemaless. Logs look similar to the following:
{"level":"info","ts":1580377225.2966235,"logger":"couchbaseutil","msg":"Cluster status","cluster":"default/cb-example","balance":"balanced","rebalancing":false}
{"level":"info","ts":1580377225.296685,"logger":"couchbaseutil","msg":"Node status","cluster":"default/cb-example","name":"cb-example-0000","version":"6.5.0","class":"all_services","managed":true,"status":"warmup"}
{"level":"info","ts":1580377225.6940928,"logger":"cluster","msg":"Pods warming up, skipping","cluster":"default/cb-example"}
{"level":"info","ts":1580377225.892829,"logger":"cluster","msg":"Reconcile completed","cluster":"default/cb-example"}
{"level":"info","ts":1580377226.7565176,"logger":"cluster","msg":"Creating XDCR remote cluster","cluster":"default/cb-example","remote":"remote"}The Operator uses the Uber Zap library to generate logging information. Each entry is organized as a JSON object with key/value pairs of information.
Some attributes are fixed and can be reliably used in your logging infrastructure and are documented in the following sections.
Zap Attributes
- level
-
This is the log level the message was emitted at. Valid values are
info,error,debugand-N(where N is an integer value based on debug level). Levels that are emitted depend on Operator configuration. - ts
-
This is the message time stamp. It is given in seconds since the UNIX epoch (1 Jan 1970, 00:00:00).
- logger
-
This is the logger that generated the message. It gives information as to which module was responsible for generating the message. This attribute is of little use outside of Couchbase support requests.
- msg
-
This is the message. Each entry will have a short message explaining what us being reported. This will not contain any contextual information about what raised the message. Context is provided by other key/value pairs.