Our infrastructure integrations with the Google Cloud Platform (GCP) includes one that reports Google Cloud Functions data to our products. This document explains how to activate the GCP Cloud Functions integration and describes the data that can be reported.
Google Cloud Functions service allows running code in a serverless way. Using the Google UI, developers can create short pieces of code that are intended to do a specific function. The function can then respond to cloud events without the need to manage an application server or runtime environment.
To enable the integration follow standard procedures to connect your GCP service to New Relic.
Our integrations query your GCP services according to a polling interval, which varies depending on the integration.
- Polling frequency for GCP Cloud Functions: five minutes
- Resolution: one data point every minute
After activating the integration and then waiting a few minutes (based on the polling frequency), data will appear in the UI. To view and use your data, including links to your dashboards and alert settings, go to one.newrelic.com, in top nav click Infrastructure, click GCP, then (select an integration).
Metric data we receive from your GCP Cloud Functions integration includes:
Count of functions that executed, by status.
Time for each function to execute, in nanoseconds.
Memory used for each function, in bytes.
After March 2022, we're discontinuing support for several capabilities, including inventory data for cloud integrations. For more details, including how you can easily prepare for this transition, see our Explorers Hub post.
Inventory data we receive from your GCP Cloud Functions integration includes the following inventory.
Inventory indicated with
* are fetched only when the GCP project is linked to New Relic through a service account.
User-provided description of a function.
The name of the function (as defined in source code) that will be executed.
For functions that can be triggered by events, the policy for failed executions.
For functions that can be triggered by events, the resource(s) from which to observe events.
For functions that can be triggered by events, the hostname of the service that should be observed.
For functions that can be triggered by events, the type of event to observe.
For functions that can be triggered via HTTPS endpoint, the deployed URL for the function.
Labels for the function.
The amount of memory in MB available for a function.
The name of the function.
The Google Cloud project that the function belongs to.
The runtime in which the function is going to run.
Status of the function deployment.
The function execution timeout. Execution is considered failed and can be terminated if the function is not completed at the end of the timeout period.
The version identifier of the Cloud Function.
The zone where the function is running.