GCP Workflows

Google Cloud Platform (GCP) Workflows is a fully managed orchestration platform that executes services in an order (workflow) that you define.

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 Workflow:

Navigate to the Observe page.
Under App Integrations, click GCP Workflows.
The list view now displays.
From the list, click a 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 Workflows. See Google Cloud metrics.

Display Name	Source Metric Name	Description
Callback Steps (Count)	`await_callback_step_count`	Number of executed steps that wait for a callback.
Callback Steps (Count)	`create_callback_step_count`	Number of executed steps that create a callback.
Callback Requests (Count)	`callback_requests_count`	Number of requests made to trigger a callback.
Callback Timeouts (Count)	`callback_timeout_count`	Number of callbacks that timed out.
CMEK Protected Workflows (Count)	`cmek_protected_workflow_count`	Number of workflows deployed with CMEK protection.
Compute Slices (Count)	`compute_slice_count`	Number of compute slices executed. Steps are executed in slices of work, which depends on the of type steps being executed.
Compute Slice Latencies (ms)	`compute_slice_latencies`	Latencies from the time a compute slice was scheduled to the time it was executed.
Compute Steps (Count)	`compute_step_count`	Number of compute steps executed (e.g. "assign" and "for" steps).
Compute Step Latencies (ms)	`compute_step_latencies`	Latencies of executed compute steps.
Deployment Attempts (Count)	`deployment_attempt_count`	Number of workflow deployment attempts.
Deployment Attempt Latencies (ms)	`deployment_latencies`	Latencies of workflow deployment attempts.
Event Time To Ack Latencies (ms)	`event_time_to_ack_latencies`	Latencies from the time an event starts to the time the workflows service acknowledges it.
Event Triggers (Count)	`event_trigger_count`	Number of event triggers received.
IO Internal Requests (Count)	`io_internal_request_count`	Number of I/O requests made by a Workflow to Google services.
Pending IO Requests (Count)	`pending_io_requests`	Number of in-flight I/O requests.
IO Steps (Count)	`io_step_count`	Number of I/O steps executed.
IO Step Latencies (ms)	`io_step_latencies`	Latencies of I/O steps executed.
KMS Requests (Count)	`kms_decrypt_request_count` `kms_encrypt_request_count`	Number of KMS decrypt/encrypt requests made by the service for CMEK.
KMS Request Latencies (ms)	`kms_decrypt_latencies` `kms_encrypt_latencies`	Latencies of decrypt/encrypt requests to KMS by workflows for CMEK.
Parallel Steps (Count)	`parallel_branch_step_count` `parallel_iteration_step_count`	Number of executed steps using parallel branches/iterations.
Parallel Substeps (Count)	`parallel_branch_substep_count` `parallel_iteration_substep_count`	Number of executed steps within parallel branches/iterations.
Parallel Unhandled Exceptions Limit Hits (Count)	`parallel_unhandled_exceptions_limit_count`	Number of times the unhandled parallel exception limit was reached.

Properties (Attributes)

Cisco Cloud Observability displays the following properties for GCP Workflows.

Display Name	Source Property Name	Description
ID	`name`	The ID of the Workflow.
Name	`-`	The name of the Cloud Workflow, trimmed from the GCP `name` field.
Project ID	-	The ID of the GCP project.
Region	-	The region where the Cloud Function is deployed in, trimmed from the GCP `name` field.
State	`state`	State of the workflow deployment. Possible values: `STATE_UNSPECIFIED` `ACTIVE` `UNAVAILABLE`
Service Account	`serviceAccount`	The service account associated with the latest workflow version.
Create Time	`createTime`	The timestamp for when the workflow was created.
Update Time	`updateTime`	The timestamp for when the workflow was last updated.
Revision ID	`revisionId`	The revision assigned to the workflow.
Revision Create Time	`revisionCreateTime`	The timestamp for the latest revision of the workflow's creation.

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.