GCP Functions

Google Cloud Platform (GCP) Functions is a serverless execution environment for building and connecting cloud services.

You must configure cloud connections to monitor this entity. See Configure Google Cloud Platform Connection.

Cisco Cloud Observability displays GCP entities on the Observe page. Metrics are displayed for specific entity instances in the list and detail views.

This document contains references to third-party documentation. Splunk AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.

Detail View

To display the detail view of a GCP Function instance:

Navigate to the Observe page.
Under Compute, click GCP Functions.
The GCP Functions list view now displays.
From the list, click a function instance Name to display the detail view.
The detail view displays metrics, key performance indicators, and properties (attributes) related to the instance you selected.

Metrics and Key Performance Indicators

Cisco Cloud Observability displays the following metrics and key performance indicators (KPIs) for GCP Functions. See Google Cloud metrics.

Some GCP metrics have been modified in Cisco Cloud Observability. Metric display names and descriptions may differ from the source metric.

Display Name	Source Metric	Description
Executions (Count)	`function/execution_count`	The count of function executions broken down by status.
Execution Duration (ms)	`function/execution_times`	The distribution of function execution times, transformed to milliseconds from nanoseconds.
Active Instances (Count)	`function/instance_count`	The number of function instances, broken down by state.
Network Egress (By)	`function/network_egress`	The outgoing network traffic of the function in bytes.
Memory Usage (By)	`function/user_memory_bytes`	The distribution of the function's maximum memory usage during execution.

Properties (Attributes)

Cisco Cloud Observability displays the following properties for GCP Functions.

Display Name	Property Name	Description
Provider	`cloud.provider`	The name of the cloud provider.
Account ID	`cloud.account.id`	The ID of the GCP project.
Platform	`cloud.platform`	The `gcp_function` string, hardcoded.
Region	`cloud.region`	The geographical region where the resource is running. This value is trimmed from the GCP `name` field.
ID	`cloud.function.id`	The ID of the cloud function.
Name	`cloud.function.name`	The name of the cloud function, trimmed from the GCP `name` field.
HTTP/S Trigger	`gcp.function.http_trigger`	The HTTP/S URL by which the cloud function can be triggered.
Event Trigger ID	`gcp.function.function_trigger.id`	The ID of the event trigger or Eventarc trigger associated with the cloud function. For `GEN_1` functions, the ID of the event trigger will be constructed following the same format as the GCP `name` field.
Environment	`gcp.function.environment`	Describes whether the cloud function is 1st or 2nd generation. Possible values: `ENVIRONMENT_UNSPECIFIED` `GEN_1` `GEN_2`
Runtime	`gcp.function.runtime`	The runtime type for the cloud function. Possible values: https://cloud.google.com/functions/docs/runtime-support
Entrypoint	`gcp.function.entrypoint`	The name of the cloud function (as defined in the source code) that will be executed.
Service ID	`gcp.function.service_config.id`	The ID of the service associated with the cloud function.
Available Memory	`cloud.function.max_memory`	The amount of memory available for the cloud function.
Available CPU	`gcp.function.service_config.available_cpu`	The number of CPUs used in a single container instance.
Max Number of Instances	`gcp.function.service_config.max_instance_count`	The limit on the maximum number of cloud function instances that may coexist at a given time.
Min Number of Instances	`gcp.function.service_config.min_instance_count`	The limit on the minimum number of cloud function instances that may coexist at a given time.
VPC Connector	`cloud.network.id`	The Serverless VPC Access connector that the cloud function can connect to.
Egress Settings	`gcp.function.service_config.egress_settings`	The egress settings for the connector, which control the type of traffic that is diverted through it. Possible values: `VPC_CONNECTOR_EGRESS_SETTINGS_UNSPECIFIED` `PRIVATE_RANGES_ONLY` `ALL_TRAFFIC`
Ingress Settings	`gcp.function.service_config.ingress_settings`	The ingress settings for the cloud function, which control the type of traffic that can reach it. Possible values: `INGRESS_SETTINGS_UNSPECIFIED` `ALLOW_ALL` `ALLOW_INTERNAL_ONLY` `ALLOW_INTERNAL_AND_GCLB`
Max Number of Instances Concurrently	`gcp.function.service_config.max_instance_request_concurrency`	The maximum number of concurrent requests that each instance can receive.
Retry Policy	`gcp.function.retry_policy`	The retry policy that will be used if the cloud function fails to execute. Possible values: `RETRY_POLICY_UNSPECIFIED` `RETRY_POLICY_DO_NOT_RETRY` (default) `RETRY_POLICY_RETRY` (up to 7 days with an exponential backoff, capped at 10 seconds)
State	`cloud.function.state`	The state of the cloud function. Possible values: `STATE_UNSPECIFIED` `ACTIVE` `FAILED` `DEPLOYING` `DELETING` `UNKNOWN`

Retention and Purge Time-To-Live (TTL)

For all cloud and infrastructure entities, the retention TTL is 180 minutes (3 hours) and the purge TTL is 525,600 minutes (365 days).

Third party names, logos, marks, and general references used in these materials are the property of their respective owners or their affiliates in the United States and/or other countries. Inclusion of such references are for informational purposes only and are not intended to promote or otherwise suggest a relationship between Splunk AppDynamics and the third party.