Monitoring Google Cloud Storage

Supported information

Supported client-side tracing

For this technology, Instana supports client-side tracing for the following languages and runtimes:

Setup

The Instana Google Cloud integration uses Service Accounts to create an API connection between Google Cloud and Instana. Below are instructions for creating the service account and providing Instana the service account credentials to begin making API calls on your behalf.

  1. Navigate to Google Cloud credentials page for the Google Cloud project you would like to setup the Instana integration.
  2. Click CREATE CREDENTIALS > Service account.

SelectServiceAccount

  1. On the Create service account page, enter a unique name for the service account, and click CREATE AND CONTINUE.

  2. Select a role or create a custom one, which contains at least the following permissions:

    • monitoring.timeSeries.list
    • storage.buckets.list

    To create a custom role, complete the following steps:

    1. From the navigation menu, click Roles > CREATE ROLE.
    2. Enter the title of the role, and click ADD PERMISSIONS.
    3. Add the basic permissions that are mentioned previously, which are required for the role, and click CREATE.

  3. Select the account you created from the list of service accounts.

  4. Select the KEYS tab, and click ADD KEY.

  5. Select Create new key and select the key type as JSON, and then click CREATE.

serviceaccountkey

You need to record the location of the credential file where it is saved to complete the integration.

  1. Add a field credentials_path to the configuration.yml file with the path to the credentials file. For example, see configuration.

In order to monitor project(s) the following services need to be enabled:

Configuration

You can configure the Google Cloud Storage metrics poll rate in seconds by adding the following configuration to the configuration file of the GCP Agent:

com.instana.plugin.gcp.storage:
  enabled: true
  poll_rate: 60 # How often Google's monitoring API will be polled in seconds
  credentials_path: '/opt/instana/credentials/cred-gcp.json' # Path to Service Account credentials
  include_tags: ''
  exclude_tags: ''

Filtering

Multiple tags can be defined, separated by a comma. Tags should be provided as a key-value pair separated by the : character. In order to make configuration easier, it is possible to define which tags you want to include in discovery or exclude from discovery. In case of defining tag in both lists (include and exclude), exclude list has higher priority. If there is no need for services filtering, the configuration should not be defined. It’s not mandatory to define all values in order to enable filtering.

To include services by tags into discovery use following configuration:

com.instana.plugin.gcp.storage:
  include_tags: # Comma separated list of tags in key:value format (e.g. env:prod,env:staging)

To exclude services by tags from discovery use following configuration:

com.instana.plugin.gcp.storage:
  exclude_tags: # Comma separated list of tags in key:value format (e.g. env:dev,env:test)

Metrics collection

To view the metrics, select Infrastructure in the sidebar of the Instana User interface, click a specific monitored host, and then you can see a host dashboard with all the collected metrics and monitored processes.

Configuration data

  • Name
  • ID
  • Project Number
  • Region
  • Location Type
  • Storage Class
  • Creation Time
  • Last Update

Performance metrics

Metric Description Granularity
Requests Delta count of API calls. 60 seconds
Object writes Delta count of API write calls. 60 seconds
Objects read Delta count of API read calls. 60 seconds
Objects count Total number of objects per bucket. 300 seconds / Sampled once per day.
Objects size Total size of all objects in the bucket. 300 seconds / Sampled once per day.
Received bytes Delta count of bytes received over the network. 300 seconds
Sent bytes Delta count of bytes sent over the network.. 300 seconds

Health signatures

For each sensor, there is a curated knowledgebase of health signatures that are evaluated continuously against the incoming metrics and are used to raise issues or incidents depending on user impact.

Built-in events trigger issues or incidents based on failing health signatures on entities, and custom events trigger issues or incidents based on defined thresholds of any given entity's individual metrics.

For information about built-events for the Google Cloud Storage, see the Built-in events reference.