Splunk® Data Stream Processor

Connect to Data Sources and Destinations with DSP

Acrobat logo Download manual as PDF


Acrobat logo Download topic as PDF

Create a DSP connection to Google Cloud Monitoring

The Google Cloud Monitoring connector will be deprecated soon. See the Release Notes for more information.

To get metrics data from Google Cloud Monitoring into a data pipeline in Splunk Data Stream Processor (DSP), you must first create a connection using the Google Cloud Monitoring connector. In the connection settings, provide the credentials of your Google Cloud Monitoring account so that DSP can access your data, and schedule a data collection job to specify how frequently DSP retrieves the data. You can then use the connection in the Google Cloud Monitoring source function to get data from Google Cloud Monitoring into a DSP pipeline.

Prerequisites

Before you can create the Google Cloud Monitoring connection, you must have the following:

  • A Google Cloud Monitoring account with at least the following permissions, which can be granted using the monitoring.Viewer role:
    • metricDescriptors.list
    • timeSeries.list
  • The following credentials for your Google Cloud Monitoring account:
    • Private key ID
    • Private key
    • Client email

If you don't have a Google Cloud Monitoring account with the necessary permissions, ask your Google Cloud administrator for assistance. Search for "Creating and managing service account keys" in the Google Cloud Monitoring documentation for more information about creating and managing service account keys using the Google Cloud Console.

Steps

  1. From the Data Stream Processor home page, click Data Management and then select the Connections tab.
  2. Click Create New Connection.
  3. Select Google Cloud Monitoring and then click Next.
  4. Complete the following fields:
    Field Description
    Connection Name A unique name for your connection.
    Private Key ID Your Google Cloud Monitoring account private key ID.
    Private Key Your Google Cloud Monitoring account private key.
    Client Email The client email address linked to your Google Cloud Monitoring account.
    Project IDs A list of project IDs.
    Metric Types (Optional) A list of metric types that you want to collect data from. The list is used as a prefix to filter the metric types.
    Scheduled This parameter is on by default, indicating that jobs run automatically. Toggle this parameter off to stop the scheduled job from automatically running. Jobs that are currently running are not affected.
    Schedule The time-based job schedule that determines when the connector executes jobs for collecting data. Select a predefined value or write a custom CRON schedule. All CRON schedules are based on UTC.
    Workers The number of workers you want to use to collect data.

    Any credentials that you upload are transmitted securely by HTTPS, encrypted, and securely stored in a secrets manager.

  5. Click Save.

    If you're editing a connection that's being used by an active pipeline, you must reactivate that pipeline after making your changes.

You can now use your connection in a Google Cloud Monitoring source function at the start of your data pipeline to get metrics data from Google Cloud Monitoring. For instructions on how to build a data pipeline, see the Building a pipeline chapter in the Use the manual. For information about the source function, see Get data from Google Cloud Monitoring in the Function Reference manual.

Last modified on 06 March, 2021
PREVIOUS
Connecting Google Cloud Monitoring to your DSP pipeline
  NEXT
Connecting Google Cloud Pub/Sub to your DSP pipeline

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.2.0, 1.2.1


Was this documentation topic helpful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters