--- title: Manage Logging description: The Logging facility allows a record to be maintained of important events that occur on Couchbase Server. pubDate: 2026-08-17T09:53:44.266Z antora: editUrl: https://github.com/couchbase/docs-server/edit/release/7.6/modules/manage/pages/manage-logging/manage-logging.adoc xref: xref:7.6@server:manage:manage-logging/manage-logging.adoc[] --- [Consult the llms.txt file for a full list of contents](/llms.txt) [View original HTML](/server/7.6/manage/manage-logging/manage-logging.html) # Manage Logging > The _Logging_ facility allows a record to be maintained of important events that occur on Couchbase Server. ## [](#logging%5Foverview)Logging Overview The Couchbase-Server _Logging_ facility records important events, and saves the details to log files, on disk. Additionally, events of cluster-wide significance are displayed on the **Logs** screen, in Couchbase Web Console. This may appear as follows: ![loggingScreenBasic](../_images/manage-logging/loggingScreenBasic.png) By default, on Linux systems, log files are saved to `/opt/couchbase/var/lib/couchbase/logs`; on MacOS, to `/Users/username/Library/Application Support/Couchbase/var/lib/couchbase/logs`; and on Windows, to `C:\Program Files\Couchbase\Server\var\lib\couchbase\logs`. ## [](#collecting%5Finformation)Collecting Information On each node within a Couchbase Server-cluster, logging is performed continuously. _A subset_ of the results can be reviewed in the Couchbase Web Console **Logs** screen; while _all_ details are saved to the `logs` directory, as described above. (Note that the `logs` directory may include `audit.log`. This is a special log file, used to manage cluster-security, and is handled separately from the other log files. The information provided throughout the remainder of this page — on collecting, uploading, redacting, and more — _does not_ apply to `audit.log`. For information on `audit.log`, see [Auditing](../../learn/security/auditing.md).) Additionally, _explicit logging_ can be performed by the user. This allows comprehensive and fully updated information to be generated as required. The output includes everything currently on disk, together with additional data that is gathered in real time. Explicit logging can either be performed for all nodes in the cluster, or for one or more individual nodes. The results are saved as zip files: each zip file contains the log-data generated for an individual node. Explicit logging can be performed by means of the Couchbase CLI utility `cbcollect_info`. The documentation for this utility, provided [here](../../cli/cbcollect-info-tool.md), includes a complete list of the log files that can be created, and a description of the contents of each. Additionally, administrators with either the **Full Admin** or **Cluster Admin** role can perform explicit logging by means of Couchbase Web Console: on the **Logs** page, left-click on the **Collect Information** tab, located near the top. (Note that for administrators without either of these roles, this tab does not appear.) ![collectInfo](../_images/manage-logging/collectInfo.png) This brings up the **Collect Information** screen: ![collectInformationScreen](../_images/manage-logging/collectInformationScreen.png) This allows logs and diagnostic information to be collected either from all or from selected nodes within the cluster. It also allows, in the **Redact Logs** panel, a log redaction-level to be specified (this is described in [Applying Redaction](#applying%5Fredaction), below). The **Specify custom temp directory** checkbox can be checked to specify the absolute pathname of a directory into which data is temporarily saved, during the collection process. The **Specify custom destination directory** can be checked to specify the absolute pathname of a directory into which the completed zip files are saved. The **Upload to Couchbase** checkbox is described in [Uploading Log Files](#uploading%5Flog%5Ffiles), below. To start the collection-process, left-click on the **Start Collecting** button. A notification is displayed, indicating that the collection-process is running. A button is provided to allow the collection-process to be stopped, if this should be appropriate. Whenever the collection-process completes for one of the nodes, a notification is displayed, and the collection-process continues, if necessary, for remaining nodes. When the process has completed for all nodes, information is displayed as follows: ![collectInformationComplete](../_images/manage-logging/collectInformationComplete.png) As this indicates, a set of log files has been created for each node in the cluster. Each file is saved as a zip file in the stated temporary location. ## [](#uploading%5Flog%5Ffiles)Uploading Log Files Log files can be uploaded to Couchbase, for inspection by Couchbase Support. For information on performing upload at the command-prompt, see [cbcollect\_info](../../cli/cbcollect-info-tool.md). To upload by means of Couchbase Web Console, before starting the collection-process, check the **Upload to Couchbase** checkbox: ![uploadToCouchbaseCheckbox](../_images/manage-logging/uploadToCouchbaseCheckbox.png) The display changes to the following: ![uploadToCouchbaseDialogBasic](../_images/manage-logging/uploadToCouchbaseDialogBasic.png) The dialog now features an **Upload to Host** field, which contains the server-location to which the customer-data is uploaded. Fields are also provided for **Customer Name** (required) and **Ticket Number** (optional). The **Upload Proxy** field optionally takes the hostname of a remote system, which contains the directory specified by the pathname. If the **Bypass Reachability Checks** checkbox is left unchecked (which is the default), an attempt is made to gather and upload the collected information without the upload specifications (that is, the upload host, customer name, and optionally, upload proxy) being pre-verified. Otherwise, if the checkbox _is_ checked, the upload specifications are submitted for verification _before_ information is collected and attemptedly uploaded: in which case, if the upload specifications cannot be verified, the collection-operation does not proceed, and an error is flagged on the console. When all required information has been entered, to start information-collection, left-click on the **Start Collecting** button. When collection and upload have been successfully completed, the URL of the uploaded zip file is displayed. ## [](#getting-a-cluster-summary)Getting a Cluster Summary A summary of the cluster's status can be acquired by means of the link at the lower right of the **Collect Information** panel: ![getClusterSummaryLink](../_images/manage-logging/getClusterSummaryLink.png) This brings up the **Cluster Summary Info** dialog: ![clusterSummaryInfoDialog](../_images/manage-logging/clusterSummaryInfoDialog.png) This displayed JSON document, which contains detailed status on the current configuration and status of the entire cluster, can be copied to the clipboard, by left-clicking on the **Copy to Clipboard** button, at the lower left. This information can then be manually shared with Couchbase Support; either in addition to, or as an alternative to log-collection. ## [](#understanding%5Fredaction)Understanding Redaction Optionally, log files can be _redacted_. This means that user-data, considered to be private, is removed. Such data includes: * Key/value pairs in JSON documents * Usernames * Query-fields that reference key/value pairs and/or usernames * Names and email addresses retrieved during product registration * Extended attributes This redaction of user-data is referred to as _partial_ redaction. (_Full_ redaction, which will be available in a forthcoming version of Couchbase Server, additionally redacts _meta-data_.) In each modified log file, hashed text (achieved with SHA1) is substituted for redacted text. For example, the following log file fragment displays private data — a Couchbase username: ```bash 0ms [I0] {2506} [INFO] (instance - L:421) Effective connection string: couchbase://127.0.0.1?username=Administrator&console_log_level=5&;. Bucket=default ``` The redacted version of the log file might appear as follows: ```bash 0ms [I0] {2506} [INFO] (instance - L:421) Effective connection string: e07a9ca6d84189c1d91dfefacb832a6491431e95. Bucket=e16d86f91f9fd0b110be28ad00e348664b435e9e ``` Note that redaction may eliminate some parameters containing non-private data, as well as all parameters containing private. Note also that redaction of log files may have one or both of the following consequences: * Logged issues will be found harder to diagnose, by both the user and Couchbase Support. * Log-collection is significantly more time-consumptive, since redaction is performed at collection-time. ## [](#applying%5Fredaction)Applying Redaction Redaction of log files saved on the cluster can be applied as required, when performing _explicit logging_, by means of either `cbcollect_info` or the **Logs** facility of Couchbase Web Console. For information on performing explicit logging with redaction at the command-prompt, see [cbcollect\_info](../../cli/cbcollect-info-tool.md). To perform explicit logging with redaction by means of Couchbase Web Console, before starting the collection-process, access the **Redact Logs** panel, on the **Collect Information** screen. This features two radio-buttons, labeled **No Redaction** and **Partial Redaction**. Make sure the **Partial Redaction** radio-button is selected. Guidance on redaction is displayed below it: ![partialRedactionSelection](../_images/manage-logging/partialRedactionSelection.png) Left-click on the **Start Collecting** button. A notification explains that the collection-process is now running. When the process has completed, a further notification appears, specifying the location (local or remote) of each created zip file. Note that, when redaction has been specified, two zip files are provided for each node: one file containing redacted data, the other unredacted data. ## [](#redacting-log-files-outside-the-cluster)Redacting Log Files Outside the Cluster Certain Couchbase technologies — such as `cbbackupmgr`, the SDK, connectors, and Mobile — create log files saved outside the Couchbase Cluster. These can be redacted by means of the command-line tool `cblogredaction`. Multiple log files can be specified simultaneously. Each file must be specified as plain text. Optionally, the salt to be used can be automatically generated. For example: ```bash $ cblogredaction /Users/username/testlog.log -g -o /Users/username -vv 2018/07/17T11:27:06 WARNING: Automatically generating salt. This will make it difficult to cross reference logs 2018/07/17T11:27:07 DEBUG: /Users/username/testlog.log - Starting redaction file size is 19034284 bytes 2018/07/17T11:27:07 DEBUG: /Users/username/testlog.log - Log redacted using salt: COeAtexHB69hGEf3 2018/07/17T11:27:07 INFO: /Users/username/testlog.log - Finished redacting, 50373 lines processed, 740 tags redacted, 0 lines with unmatched tags ``` For more information, see the corresponding man page, or run the command with the `--h` (help) option. ## [](#log-file-locations)Log File Locations Couchbase Server creates log files in the following locations. | Platform | Location | | -------- | ------------------------------------------------------------------------------------------------------- | | Linux | _/opt/couchbase/var/lib/couchbase/logs_ | | Windows | _C:\\Program Files\\Couchbase\\Server\\var\\lib\\couchbase\\logs_ Assumes default installation location | | Mac OS X | _/Users//Library/Application Support/Couchbase/var/lib/couchbase/logs_ | ## [](#log-file-listing)Log File Listing The following table lists the log files to be found on Couchbase Server. Unless otherwise specified, each file is named with the `.log` extension. | File | Log Contents | | --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | audit | Security audit log for administrators. | | babysitter | Troubleshooting log for the babysitter process which is responsible for spawning all Couchbase Server processes and respawning them where necessary. | | backup\_service | Log for Backup Service; containing entries at debug, info, warn, and error levels. | | couchdb | Troubleshooting log for the couchdb subsystem which underlies map-reduce. | | debug | Debug-level troubleshooting for the Cluster Manager. | | error | Error-level troubleshooting log for the Cluster Manager. | | eventing | Troubleshooting log for the Eventing Service. | | fts | Troubleshooting log for the Search Service. | | goxdcr | Troubleshooting log for XDCR source activity. | | http\_access | The admin access log records server requests (including administrator logins) to the REST API or Couchbase Web Console. It is output in common log format and contains several important fields such as remote client IP, timestamp, GET/POST request and resource requested, HTTP status code, and so on. | | http\_access\_internal | The admin access log records internal server requests (including administrator logins) to the REST API or Couchbase Web Console. It is output in common log format and contains several important fields such as remote client IP, timestamp, GET/POST request and resource requested, HTTP status code, and so on. | | indexer | Troubleshooting log for the Index Service. | | indexer\_stats | Log containing statistics related to the Index Service. | | info | Info-level troubleshooting log for the Cluster Manager. | | json\_rpc | Log used by the cluster manager. | | mapreduce\_errors | JavaScript and other view-processing errors are reported in this file. | | memcached | Contains information relating to the core memcached component, including DCP stream requests and slow operations.It is possible to adjust the logging for slow operations. See [Adjusting Threshold for Logging Slow Operations](#adjust-threshold-slow-op-logging) for details. | | metakv | Troubleshooting log for the metakv store, a cluster-wide metadata store. | | ns\_couchdb | Contains information related to starting up the couchdb subsystem. | | projector | Troubleshooting log for the projector process which is responsible for sending appropriate mutations from Data Service nodes to Index Service nodes. | | prometheus | Log for the instance of [Prometheus](https://prometheus.io) that runs on the current node, supporting the gathering and management of Couchbase-Server _metrics_ . (See the [Metrics Reference](../../metrics-reference/metrics-reference.md), for more information.) | | query | Troubleshooting log for the Query Service. | | rebalance | Contains reports on rebalances that have occurred. Up to the last _five_ reports are maintained. Each report is named in accordance with the time it was run: for example, rebalance\_report\_2020-03-17T11:10:17Z.json. See the [Rebalance Reference](../../rebalance-reference/rebalance-reference.md), for detailed information. | | reports | Contains progress and crash reports for the Erlang processes. Due to the nature of Erlang, processes crash and restart upon an error. | | ssl\_proxy | Troubleshooting log for the ssl proxy spawned by the Cluster Manager. | | stats | Contains periodic statistic dumps from the Cluster Manager. | | views | Troubleshooting log for the views engine, predominantly focusing on the changing of partition states. | | xdcr\_target | Troubleshooting log for data received from XDCR sources. | | analytics\_access | Information on access attempts made to the REST/HTTP port of the Analytics Service. | | analytics\_cbas\_debug | Debugging information, related to the Analytics Service. | | analytics\_dcpdebug | DCP-specific debugging information related to the Analytics Service. | | analytics\_dcp\_failed\_ingestion | Information on documents that have failed to be imported/ingested from the Data Service into the Analytics Service. | | analytics\_debug | Events logged by the Analytics Service at the DEBUG logging level. | | analytics\_error | Events logged by the Analytics Service at the ERROR logging level. | | analytics\_info | Events logged by the Analytics Service at the INFO logging level. | | analytics\_shutdown | Information concerning the shutting down of the Analytics Service. | | analytics\_warn | Events logged by the Analytics Service at the WARN logging level. | ## [](#log-file-rotation)Log File Rotation The `memcached` log file is rotated when it has reached 10MB in size; twenty rotations being maintained — the current file, plus nineteen compressed rotations. Other logs are automatically rotated after they have reached 40MB in size; ten rotations being maintained — the current file, plus nine compressed rotations. To provide custom rotation-settings for each component, add the following to the `static_config` file: {disk_sink_opts_disk_debug, [{rotation, [{size, 10485760}, {num_files, 10}]}]}. This rotates the `debug.log` at 10MB, and keeps ten copies of the log: the current log and nine compressed logs. Log rotation settings can be changed. Note, however, that this is not advised; and that only the default log rotation settings are supported by Couchbase. ## [](#changing-log-file-locations)Changing Log File Locations The default log location on Linux systems is _/opt/couchbase/var/lib/couchbase/logs_. The location can be changed. Note, however, that this is not advised; and that only the default log location is supported by Couchbase. To change the location, proceed as follows: 1. Log in as `root` or `sudo` and navigate to the directory where Couchbase Server is installed. For example: `/opt/couchbase/etc/couchbase/static_config`. 2. Edit the _static\_config_ file: change the `error_logger_mf_dir` variable, specifying a different directory. For example: `{error_logger_mf_dir, "/home/user/cb/opt/couchbase/var/lib/couchbase/logs"}` 3. Stop and restart Couchbase Server. See [Startup and Shutdown](../../install/startup-shutdown.md). ## [](#changing-log-file-levels)Changing Log File Levels The default logging level for all log files is _debug_, except for `couchdb`, which is set to _info_. Logging levels can be changed. Note, however, that this is not advised; and that only the default logging levels are supported by Couchbase. Either _persistent_ or _dynamic_ changes can be made to logging levels. ### [](#persistent-changes)Persistent Changes _Persistent_ means that changes continue to be implemented, should a Couchbase Server reboot occur. To make a persistent change on Linux systems, proceed as follows: 1. Log in as `root` or `sudo`, and navigate to the directory where you installed Couchbase. For example: `/opt/couchbase/etc/couchbase/static_config`. 2. Edit the _static\_config_ file and change the desired log component. (Parameters with the `loglevel_` prefix establish logging levels.) 3. Stop and restart Couchbase Server. See [Startup and Shutdown](../../install/startup-shutdown.md). ### [](#dynamic-changes)Dynamic Changes _Dynamic_ means that if a Couchbase Server reboot occurs, the changed logging levels revert to the default. To make a dynamic change, execute a `curl POST` command, using the following syntax: curl -X POST -u adminName:adminPassword HOST:PORT/diag/eval \ -d 'ale:set_loglevel(,).' * `log_component`: The default log level (except `couchdb`) is `debug`; for example `ns_server`. The available loggers are `ns_server`, `couchdb`, `user`, `Menelaus`, `ns_doctor`, `stats`, `rebalance`, `cluster`, views, `mapreduce_errors` , xdcr and `error_logger`. * `logging_level`: The available log levels are `debug`, `info`, `warn`, and `error`. curl -X POST -u Administrator:password http://127.0.0.1:8091/diag/eval \ -d 'ale:set_loglevel(ns_server,error).' ## [](#collecting-logs-using-cli)Collecting Logs Using the CLI To collect logs, use the CLI command [cbcollect\_info](../../cli/cbcollect-info-tool.md). To start and stop log-collection, and to collect log-status, use: * [collect-logs-start](../../cli/cbcli/couchbase-cli-collect-logs-start.md) * [collect-logs-stop](../../cli/cbcli/couchbase-cli-collect-logs-stop.md) * [collect-logs-status](../../cli/cbcli/couchbase-cli-collect-logs-status.md) ## [](#collecting-logs-using-rest)Collecting Logs Using the REST API The Logging REST API provides the endpoints for retrieving log and diagnostic information. To retrieve log information use the `/diag` and `/sasl_logs` [REST endpoints](../../rest-api/logs-rest-api.md). ## [](#adjust-threshold-slow-op-logging)Adjusting Threshold for Logging Slow Operations It is possible to examine and/or alter the logging threshold for slow-running operations. This is done using the `mcctl` command that comes packaged with the Couchbase server installation. The command only gets or sets information for the node it's run on. ### [](#getting-threshold-details)Getting Threshold Details The current settings are retrieved by using the `mcctl` cli to execute the `get sla` command: > [!IMPORTANT] > These settings only apply to the nodes _where the changes are made._ > > You must implement the changes on each node to ensure they are applied across the cluster. > > You must also configure the node to run the `data service`. Getting threshold details ```bash /opt/couchbase/bin/mcctl --host localhost -u Administrator -P password \ get sla ``` Result ```json {"comment":"Current MCBP SLA configuration", "version":1, "default":{"slow":"500 ms"}}, "COMPACT_DB":{"slow":"1800 s"}, "DELETE_BUCKET":{"slow":"10 s"}, "SEQNO_PERSISTENCE":{"slow":"30 s"} } ``` The JSON message returned gives details of the operation being logged and the threshold time that will cause a timing message to be logged. ### [](#setting-the-threshold)Setting the Threshold The `mcctl` command line interface is also used to set the thresholds for the memcahe operations: Set logging threshold example ```bash /opt/couchbase/bin/mcctl --host localhost -u Administrator -P password \ set sla '{"version":1, "DELETE_BUCKET":{"slow":"100 ms"}}' ``` In this example, the threshold for the `DELETE_BUCKET` operation is being set to 100ms. If a bucket deletion operation takes longer than this, then an message will be logged. > [!TIP] > As an added minor convenience, the time interval can also be specified without a space: > > ```bash > /opt/couchbase/bin/mcctl --host localhost -u Administrator -P password \ > set sla '{"version":1, "DELETE_BUCKET":{"slow":"100ms"}}' > ``` It is also possible to set the threshold for all the op-codes in a single command by using the `default` code: Set all thresholds to 100 ms. ```bash /opt/couchbase/bin/mcctl --host localhost -u Administrator -P password \ set sla '{"version":1, "default":{"slow":"100 ms"}}' ``` Time units in threshold settings A number of different time units can be used when setting the thresholds: | **ns** | nanoseconds | | ------ | ------------ | | **us** | microseconds | | **ms** | milliseconds | | **s** | seconds | | **m** | minutes | | **h** | hours | Setting the `DELETE_BUCKET` threshold to 1 minute. ```bash /opt/couchbase/bin/mcctl --host localhost -u Administrator -P password \ set sla '{"version":1, "DELETE_BUCKET":{"slow":"1 m"}}' ``` Setting the threshold values is non-persistent: when the node is restarted, the thresholds are reset to their default values. ### [](#setting-threshold-defaults)Setting Threshold Defaults The default values are loaded from the file: `/opt/couchbase/etc/couchbase/kv/opcode-attributes.json` when the node is started. ```json { "comment": "Default configuration file. Do not edit, but override the settings in opcode-attributes.d/", "version": 1, "default": { "slow": "500 ms" }, "compact_db": { "slow": "30 m" }, "create_bucket": { "slow": "70 ms" }, "select_bucket": { "slow": "10 ms" }, "delete_bucket": { "slow": "10 s" }, "seqno_persistence": { "slow": "30 s" } } ``` These values can be overriden by creating another file in the `/opt/couchbase/etc/couchbase/kv/opcode-attributes.d` directory. The easiest way to do this is to copy the existing settings file into the directory, making sure that there isn't an existing file in the directory: ```bash cd /opt/couchbase/etc/couchbase/kv/ cp opcode-attributes.json opcode-attributes.d ``` Edit `/opt/couchbase/etc/couchbase/kv/opcode-attributes.d/opcode-attributes.json` with the new settings. > [!NOTE] > These settings only apply to the node where the changes are made. To change the threshold across the cluster, then all the configurations must be applied to each node.