All DSP releases prior to DSP 1.4.0 use Gravity, a Kubernetes orchestrator, which has been announced end-of-life. We have replaced Gravity with an alternative component in DSP 1.4.0. Therefore, we will no longer provide support for versions of DSP prior to DSP 1.4.0 after July 1, 2023. We advise all of our customers to upgrade to DSP 1.4.0 before July 1, 2023 in order to continue to receive full product support from Splunk.
Create a DSP connection to Google Cloud Monitoring
The Google Cloud Monitoring connector is planned for deprecation. See the Release Notes for more information.
To get metrics data from Google Cloud Monitoring into a data pipeline in Splunk Data Stream Processor, 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.
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
- 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.
- In DSP, select the Connections page.
- On the Connections page, click Create Connection.
- On the Source tab, select Google Cloud Monitoring and then click Next.
- 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.
- 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. When you reactivate a pipeline, you must select where you want to resume data ingestion. See Using activation checkpoints to activate your pipeline in the Use the Data Stream Processor manual for more information.
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 Data Stream Processor manual. For information about the source function, see Get data from Google Cloud Monitoring in the Function Reference manual.
Connecting Google Cloud Monitoring to your DSP pipeline
Connecting Google Cloud Pub/Sub to your DSP pipeline
This documentation applies to the following versions of Splunk® Data Stream Processor: 1.3.0, 1.3.1
Feedback submitted, thanks!