GCP Cloud Tasks

Google Cloud Platform (GCP) Cloud Tasks is a fully managed service that allows you to manage the execution, dispatch and delivery of a large number of distributed tasks.

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 Cloud Task instance:

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

Display Name	Source Metric	Description
Queue Depth (Count)	`queue/depth`	The number of tasks in the queue.
Task Attempts (Count)	`queue/task_attempt_count`	The count of task attempts broken down by response code.
Task Attempt Delays (ms)	`queue/task_attempt_delays`	The delay between each scheduled attempt time and actual attempt time.

Properties (Attributes)

Cisco Cloud Observability displays the following properties for GCP Cloud Task.

Display Name	Source Property Name	Description
ID	`name`	The queue ID, in the format `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID`.
Name	-	The queue name.
Project ID	-	The ID of the GCP project.
Region	-	The location of the node.
State	`state`	The state of the queue. Possible values: `STATE_UNSPECIFIED`, `RUNNING`, `PAUSED`, `DISABLED`.
Purge Time	`purgeTime`	The last time this queue was purged.
Retry Maximum Number of Attempts	`retryConfig.maxAttempts`	The number of attempts per task. Cloud Tasks will attempt the task `maxAttempts` times. If the first attempt fails, then there will be `maxAttempts` - 1 retries. The value of this property must be >= -1. If the value is unspecified when the queue is created, Cloud Tasks will pick the default. -1 indicates unlimited attempts.
Retry Maximum Duration (s)	`retryConfig.maxRetryDuration`	If the value is `positive`, `maxRetryDuration` specifies the time limit for retrying a failed task, measured from when the task was first attempted. Once the `maxRetryDuration` time has passed and the task has been attempted `maxAttempts` times, no further attempts will be made and the task will be deleted. If the value is `zero`, then the task age is unlimited. If the value is unspecified when the queue is created, Cloud Tasks will pick the default. The value must be given as a string that indicates the length of time (in seconds) followed by s (for "seconds"). For the maximum possible value or the format, see the documentation for Duration. `maxRetryDuration` will be truncated to the nearest second.
Retry Minimum Backoff (s)	`retryConfig.minBackoff`	A task will be scheduled for retry between `minBackoff` and `maxBackoff` duration after it fails, if the queue's `RetryConfig` specifies that the task should be retried. If the value is unspecified when the queue is created, Cloud Tasks will pick the default. The value must be given as a string that indicates the length of time (in seconds) followed by s (for "seconds"). For more information on the format, see the documentation for Duration. `minBackoff` will be truncated to the nearest second.
Retry Maximum Backoff (s)	`retryConfig.maxBackoff`	A task will be scheduled for retry between minBackoff and maxBackoff duration after it fails, if the queue's RetryConfig specifies that the task should be retried. If the value is unspecified when the queue is created, Cloud Tasks will pick the default. The value must be given as a string that indicates the length of time (in seconds) followed by s (for "seconds"). For more information on the format, see the documentation for Duration. `maxBackoff` will be truncated to the nearest second.
Retry Maximum Doublings	`retryConfig.maxDoublings`	The time between retries will double `maxDoublings` times. A task's retry interval starts at `minBackoff`, then doubles `maxDoublings` times, then increases linearly, and finally retries at intervals of `maxBackoff` up to `maxAttempts` times. For example, if `minBackoff` is 10s, `maxBackoff` is 300s, and `maxDoublings` is 3, then the a task will first be retried in 10s. The retry interval will double three times, and then increase linearly by 2^3 * 10s. Finally, the task will retry at intervals of `maxBackoff` until the task has been attempted `maxAttempts` times. Thus, the requests will retry at 10s, 20s, 40s, 80s, 160s, 240s, 300s, 300s, .... If the value is unspecified when the queue is created, Cloud Tasks will pick the default.
Rate Limit Maximum Dispatches Per Second	`rateLimits.maxDispatchesPerSecond`	The maximum rate at which tasks are dispatched from this queue. If the value is unspecified when the queue is created, Cloud Tasks will pick the default. The maximum allowed value is 500.
Rate Limit Maximum Burst Size	`rateLimits.maxBurstSize`	Max burst size limits how fast tasks in queue are processed when many tasks are in the queue and the rate is high. This field allows the queue to have a high rate so processing starts shortly after a task is enqueued, but still limits resource usage when many tasks are enqueued in a short period of time. The token bucket algorithm is used to control the rate of task dispatches. Each queue has a token bucket that holds tokens, up to the maximum specified by `maxBurstSize`. Each time a task is dispatched, a token is removed from the bucket. Tasks will be dispatched until the queue's bucket runs out of tokens. The bucket will be continuously refilled with new tokens based on `maxDispatchesPerSecond`. Cloud Tasks will pick the value of `maxBurstSize` based on the value of `maxDispatchesPerSecond`.
Rate Limit Maximum Concurrent Dispatches	`rateLimits.maxConcurrentDispatches`	The maximum number of concurrent tasks that Cloud Tasks allows to be dispatched for this queue. After this threshold has been reached, Cloud Tasks stops dispatching tasks until the number of concurrent requests decreases. If the value is unspecified when the queue is created, Cloud Tasks will pick the default. The maximum allowed value is 5,000.

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.