Couchbase Stay organized with collections Save and categorize content based on your preferences.
The Couchbase integration collects bucket metrics such as operations,memory usage, and ejections. The integration collects metrics from thePrometheus server exposed on a node. The integration also collects Couchbasegeneral, HTTP access, and cross-datacenter ("goxdcr") logs.
For more information about Couchbase, see theCouchbase documentation.
Prerequisites
To collect Couchbase telemetry, you mustinstall the Ops Agent:
- For metrics, install version 2.18.2 or higher.
- For logs, install version 2.18.2 or higher.
This integration supports Couchbase versions 6.5, 6.6, and 7.0.
Configure the Ops Agent for Couchbase
Following the guide toConfigure the OpsAgent, add the required elementsto collect telemetry from Couchbase instances, andrestart the agent.
Example configuration
The following commands create the configuration to collect and ingest telemetryfor Couchbase:
#ConfiguresOpsAgenttocollecttelemetryfromtheapp.Youmustrestarttheagentfortheconfigurationtotakeeffect.set-e#Checkifthefileexistsif[!-f/etc/google-cloud-ops-agent/config.yaml];then#Createthefileifitdoesn'texist.sudomkdir-p/etc/google-cloud-ops-agentsudotouch/etc/google-cloud-ops-agent/config.yamlfi#Createabackupoftheexistingfilesoexistingconfigurationsarenotlost.sudocp/etc/google-cloud-ops-agent/config.yaml/etc/google-cloud-ops-agent/config.yaml.bak#ConfiguretheOpsAgent.sudotee/etc/google-cloud-ops-agent/config.yaml >/dev/null <<EOFmetrics:receivers:couchbase:type:couchbaseusername:adminpassword:password#Tousethegooglesecretmanagerprovidertoreplaceplaintextpasswords,refertotheexamplebelow.#password:${googlesecretmanager:projects/<project-id>/secrets/<secret-id>/versions/<version-id>}collection_interval:30sservice:pipelines:couchbase:receivers:-couchbaselogging:receivers:couchbase_general:type:couchbase_generalcouchbase_http_access:type:couchbase_http_accesscouchbase_goxdcr:type:couchbase_goxdcrservice:pipelines:couchbase:receivers:-couchbase_general-couchbase_http_access-couchbase_goxdcrEOFFor these changes to take effect, you must restart the Ops Agent:
Linux
- To restart the agent, run the following command on your instance:
sudo systemctl restart google-cloud-ops-agent
- To confirm that the agent restarted, run the following command and verify that the components "Metrics Agent" and "Logging Agent" started:
sudo systemctl status "google-cloud-ops-agent*"
Windows
- Connect to your instance using RDP or a similar tool and login to Windows.
- Open a PowerShell terminal with administrator privileges by right-clicking the PowerShell icon and selectingRun as Administrator
- To restart the agent, run the following PowerShell command:
Restart-Service google-cloud-ops-agent -Force
- To confirm that the agent restarted, run the following command and verify that the components "Metrics Agent" and "Logging Agent" started:
Get-Service google-cloud-ops-agent*
What is logged
ThelogName is derived fromthe receiver IDs specified in the configuration. Detailed fields inside theLogEntryare as follows.
Thecouchbase_general logs contain the following fields in theLogEntry:
| Field | Type | Description |
|---|---|---|
jsonPayload.level | string | Log entry severity for the couchbase log |
jsonPayload.message | string | Log message |
jsonPayload.module_name | string | The name of the module issuing the entry |
jsonPayload.node_name | string | The name of the node issuing the log message |
jsonPayload.source | string | Source where the log originated |
jsonPayload.type | string | The type of log |
severity | string (LogSeverity) | Log entry level (translated). |
Thecouchbase_http_access logs contain the following fields in theLogEntry:
| Field | Type | Description |
|---|---|---|
httpRequest | object | SeeHttpRequest |
jsonPayload.host | string | The IP address of the client invoking the HTTP request |
jsonPayload.level | string | Log entry severity for the couchbase log |
jsonPayload.message | string | Log message |
jsonPayload.user | string | The name of the user making the HTTP request if basic auth is used. |
severity | string (LogSeverity) | Log entry level (translated). |
Thecouchbase_goxdcr logs contain the following fields in theLogEntry:
| Field | Type | Description |
|---|---|---|
jsonPayload.level | string | Log entry severity for the couchbase log |
jsonPayload.log_type | string | The name of the component that is issuing the cross-datacenter log |
jsonPayload.message | string | Log message |
severity | string (LogSeverity) | Log entry level (translated). |
Configure metrics collection
To ingest metrics from Couchbase, you must create a receiver for the metricsthat Couchbase produces and then create a pipeline for the new receiver.
This receiver does notsupport the use of multiple instances in the configuration, for example, tomonitor multiple endpoints. All such instances write to the same time series,and Cloud Monitoring has no way to distinguish among them.
To configure a receiver for yourcouchbase metrics, specify the followingfields:
| Field | Default | Description |
|---|---|---|
collection_interval | 60s | Atime.Duration value, such as30s or5m. |
endpoint | localhost:8091 | The URL of the node to monitor. |
password | The password used to connect to the Couchbase server. | |
type | This value must becouchbase. | |
username | The username used to connect to the Couchbase server. |
What is monitored
The following table provides the list of metrics that the Ops Agent collectsfrom the Couchbase instance.
| Metric type | |
|---|---|
| Kind, Type Monitored resources | Labels |
workload.googleapis.com/couchbase.bucket.error.oom.count | |
CUMULATIVE, INT64gce_instance | bucket_nameerror_type |
workload.googleapis.com/couchbase.bucket.item.count | |
GAUGE, DOUBLEgce_instance | bucket_namestate |
workload.googleapis.com/couchbase.bucket.item.ejection.count | |
CUMULATIVE, INT64gce_instance | bucket_name |
workload.googleapis.com/couchbase.bucket.memory.high_water_mark.limit | |
GAUGE, DOUBLEgce_instance | bucket_name |
workload.googleapis.com/couchbase.bucket.memory.low_water_mark.limit | |
GAUGE, DOUBLEgce_instance | bucket_name |
workload.googleapis.com/couchbase.bucket.memory.usage | |
GAUGE, DOUBLEgce_instance | bucket_name |
workload.googleapis.com/couchbase.bucket.operation.count | |
CUMULATIVE, INT64gce_instance | bucket_nameop |
workload.googleapis.com/couchbase.bucket.vbucket.count | |
GAUGE, DOUBLEgce_instance | bucket_namestate |
Verify the configuration
This section describes how to verify that you correctly configured theCouchbase receiver. It might take one or twominutes for the Ops Agent to begin collecting telemetry.
To verify that Couchbase logs are being sent toCloud Logging, do the following:
In the Google Cloud console, go to theLogs Explorer page:
If you use the search bar to find this page, then select the result whose subheading isLogging.
- Enter the following query in the editor, and then clickRun query:
resource.type="gce_instance"(log_id("couchbase_general") OR log_id("couchbase_http_access") OR log_id("couchbase_goxdcr"))
To verify that Couchbase metrics are being sent toCloud Monitoring, do the following:
In the Google Cloud console, go to theleaderboard Metrics explorer page:
If you use the search bar to find this page, then select the result whose subheading isMonitoring.
- In the toolbar of thequery-builder pane, select the button whose name is eithercode MQL orcode PromQL.
- Verify thatPromQL is selectedin theLanguage toggle. The language toggle is in the same toolbar thatlets you format your query.
- Enter the following query in the editor, and then clickRun query:
{"workload.googleapis.com/couchbase.bucket.memory.usage", monitored_resource="gce_instance"}
View dashboard
To view your Couchbase metrics, you must have a chart or dashboardconfigured.The Couchbase integration includes one or more dashboards for you.Any dashboards are automatically installed after you configure theintegration and the Ops Agent has begun collecting metric data.
You can also view static previews of dashboards withoutinstalling the integration.
To view an installed dashboard, do the following:
In the Google Cloud console, go to the
Dashboards page:If you use the search bar to find this page, then select the result whose subheading isMonitoring.
- Select theDashboard List tab, and then choose theIntegrations category.
- Click the name of the dashboard you want to view.
If you have configured an integration but the dashboard has not beeninstalled, then check that the Ops Agent is running. When there is nometric data for a chart in the dashboard, installation of the dashboard fails.After the Ops Agent begins collecting metrics, the dashboard is installedfor you.
To view a static preview of the dashboard, do the following:
In the Google Cloud console, go to the
Integrations page:If you use the search bar to find this page, then select the result whose subheading isMonitoring.
- Click theCompute Engine deployment-platform filter.
- Locate the entry for Couchbase and clickView Details.
- Select theDashboards tab to see a static preview. If the dashboard is installed, then you can navigate to it by clickingView dashboard.
For more information about dashboards in Cloud Monitoring, seeDashboards and charts.
For more information about using theIntegrations page, seeManage integrations.
Install alerting policies
Alerting policies instruct Cloud Monitoring to notify you whenspecified conditions occur.The Couchbase integration includes one or more alerting policies foryou to use.You can view and installthese alerting policies from theIntegrations page inMonitoring.
To view the descriptions of available alerting policies and install them, do the following:
In the Google Cloud console, go to the
Integrations page:If you use the search bar to find this page, then select the result whose subheading isMonitoring.
- Locate the entry for Couchbase and clickView Details.
- Select theAlerts tab. This tab provides descriptions of available alerting policies and provides an interface for installing them.
- Install alerting policies. Alerting policies need to know where to send notifications that the alert has been triggered, so they require information from you for installation. To install alerting policies, do the following:
- From the list of available alerting policies, select those that you want to install.
In theConfigure notifications section, select one or more notification channels. You have the option to disable the use of notification channels, but if you do, then your alerting policies fire silently. You can check their status in Monitoring, but you receive no notifications.
For more information about notification channels, seeManage notification channels.
- ClickCreate Policies.
For more information about alerting policies in Cloud Monitoring, seeIntroduction to alerting.
For more information about using theIntegrations page, seeManage integrations.
What's next
For a walkthrough on how to use Ansible to install the Ops Agent, configurea third-party application, and install a sample dashboard, see theInstall the Ops Agent to troubleshoot third-party applications video.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-12-15 UTC.