Download PDF
Download page GCP Filestore.
GCP Filestore
GCP Filestore instances are fully managed NFS file servers on Google Cloud for use with applications running on Compute Engine virtual machine (VM) instances, Google Kubernetes Engine clusters, external datastores such as Google Cloud VMware Engine, or your on-premises machines.
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 Filestore instance:
- Navigate to the Observe page.
- Under Database & Storage, click GCP Filestore Instances.
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 Filestore.
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 Name | Description |
---|---|---|
Operations Latency (ms) |
| The average latency for all disk operations. This metric is not populated for basic tier instances. |
Instance Availability (True/False) | nfs/server/instance_available | True if the e2e NFS prober using sec=krb5 is able to probe the instance. |
Disk Capacity (By) |
| The total free/used bytes. |
Disk Capacity (%) |
| The free/used disk space as a percentage of the total space. |
Free Raw Disk Capacity (%) | nfs/server/free_raw_capacity_percent | The free raw capacity, as a percentage of the total space. |
Operations (Count) |
| The count of disk/metadata operations. |
Operations Size (By) |
| The bytes read/written from the disk. |
Operations Duration (ms) |
| The count of milliseconds spent on disk operations. |
Snapshots Size (By) | nfs/server/snapshots_used_bytes | The number of bytes used by the snapshots. |
Procedure Calls (Count) | nfs/server/procedure_call_count | The NFS server procedure call count. |
Domain Controllers (True/False) | nfs/server/domain_reachable | True if at least one of the active directory domain controllers (AD DCs) is reachable. |
Properties (Attributes)
Cisco Cloud Observability displays the following properties for GCP Filestore.
Display Name | Source Property Name | Description |
---|---|---|
ID | name | The ID of the Filestore. |
Name | - | The name of the Filestore. |
Project ID | - | The ID of the GCP project. |
Region | - | The region where the job is deployed in, trimmed from the GCP name field. |
Zone | - | The geographical region the resource is running. |
State | state | The instance state. |
Status Message | statusMessage | Additional information about the instance state, if available. |
Create Time | createTime | The time when the instance was created. |
Tier | tier | The service tier of the instance. |
ETag | etag | The server-specified ETag for the instance resource. Used to prevent simultaneous updates from overwriting each other. |
Satisfies Pzs | satisfiesPzs | Reserved for future use. |
KMS Key Name | kmsKeyName | The Key Management Service (KMS) key name used for data encryption. |
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.