Skip to main content

Setup Google StackDriver for CockroachDB

Setup Google StackDriver for CockroachDB

The following steps install and configure StackDriver for a self hosted deployment of CockroachDB.

  • Install the agent on CockroachDB VMs
  • Configure agent to point to CockroachDB logs
  • Restart agent
  • Verify logs in StackDriver

A majority of these steps can be found in Google Docs: https://cloud.google.com/logging/docs/agent/logging/installation

Manual Setup

Install the agent on CockroachDB VMs

curl -sSO https://dl.google.com/cloudagents/add-logging-agent-repo.sh
sudo bash add-logging-agent-repo.sh --also-install

Configure agent to point to CockroachDB logs

Create cockroachdb.conf file with the following contents:

<source>
  @type tail
  format none
  path /home/ubuntu/logs/*.log
  pos_file /var/lib/google-fluentd/pos/cockroachdb.pos
  read_from_head true
  tag cockroachdb
</source>

Look in cockroachdb.conf and confirm the logging directory where CockroachDB is landing the log files

...
path /home/ubuntu/logs/*.log
...

Put cockroachdb.conf config in fluentd config folder

scp -pr cockroachdb.conf <user>@<gce host>/etc/google-fluentd/config.d/cockroachdb.conf

Depending on your permissions, you may have to copy to your home folder first and then sudo cp in the config.d directory

Restart agent

sudo service google-fluentd force-reload

Check status

sudo service google-fluentd status

The output should look like this:

1: ● google-fluentd.service - LSB: data collector for Treasure Data
Loaded: loaded (/etc/init.d/google-fluentd; bad; vendor preset: enabled)
Active: active (running) since Mon 2022-01-24 18:41:59 UTC; 2min 44s ago
...

Verify Logs in StackDriver

StackDriver

Roachprod Steps

If you would like to automate the setup using roachprod, the following script should set this us for your entire cluster.

roachprod run chrisc-test -- curl -sSO https://dl.google.com/cloudagents/add-logging-agent-repo.sh
roachprod run chrisc-test -- sudo bash add-logging-agent-repo.sh --also-install
roachprod put chrisc-test -- cockroachdb.conf cockroachdb.conf
roachprod run chrisc-test -- sudo cp cockroachdb.conf /etc/google-fluentd/config.d/cockroachdb.conf
roachprod run chrisc-test -- sudo service google-fluentd force-reload
roachprod run chrisc-test -- sudo service google-fluentd status

Miscellaneous Materials

view raw stackdriver_cockroachdb.md hosted with ❤ by GitHub

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Part & Pin for the Inverted Index Win

Part & Pin for the Inverted Index Win "How to Partition Inverted Indexes in CockroachDB" Recently I worked with a CockroachDB user who had a GDPR locality requirement.  Naturally CockroachDB was a fit since it sports geo-partitioning capabilities for data and objects.  However, the user ran into a snafu where they could not partition and localize data in inverted indexes.  The example they had was customer data existed in a JSONB data column that had an inverted index on it.  The data in the table was already partitioned by country and pinned to servers / nodes that were in that country.  So they were good with table partitioning and pinning.  But the data in the inverted index could theoretically be distributed anywhere in the cluster and also needed to be partitioned and pinned to the proper locality.  I.e.  A German customer must remain in Germany.  This caught me by surprise as well that you can not partition inverted indexes o...
Post a Comment
Read more