Collect Logs & Diagnostic Information(UI)

  • upload couchbase is checkmarked

#upload to host
#coustemer name

what should i give here host and name?
(i used “” once , showed one http link and ran that in terminal it showed reacted file , is that a crrt way??)

Hello @boby,

As explained in the documentation this is used to upload the logs directly to Couchbase Support. The host name should be the one pre-filled in, and the customer name should be your company name. This option only useful if you are working directly with Couchbase Support or Pre-sales. Otherwise there is no point in using it, if you wish to look at the logs yourself then you can unclick the upload option.

(i used “” once , showed one http link and ran that in terminal it showed reacted file , is that a crrt way??)

Not sure what you mean by “it showed reacted file”, do you mean redacted?

i understood tq @pvarley

and in " /opt/couchbase/var/lib/couchbase/logs/eventing.log ." it will be collecting all log of eventing (live)
but please can you say that, does that eventing.log will be permanent in .txt file any where so that we can do filter and other stuff??



The log file /opt/couchbase/var/lib/couchbase/logs/eventing.log is for system level logging keep in mind this is not the file the output of the log(…) statements in your actual Javascript code for your Eventing functions. What goes into this log file is supervisor information for the Eventing servers and house keeping information on the Function’s life cycle (not the logic of the Function). An end user can not write a message (via a Function handler) to this log file it is intended for debugging for customers that are on support contracts. I believe redaction in the context of system logs is for things like cURL credentials.


The log(…) statements that you as a user add to your JavaScript go to handler specific logs live in a different set of rolling log files /opt/couchbase/var/lib/couchbase/data/@eventing/<<function_name>>.log . The information that goes to these log files is solely dependent the business logic of the Function via log(…) statements put inside the individual Function’s JavaScript. These files are not uploaded to support.


I’m not very clear on why you would want to “do filter and other stuff” on either log file type.

1 Like


tq .
ur information gave some idea about log.