File System Metrics

You can monitor the health, capacity, and performance of your file systems and mount targets by using metrics , alarms , and notifications.

This topic describes the metrics emitted by the metric namespace oci_filestorage (the File Storage service).

Overview of Metrics for oci_filestorage

File Storage service metrics help you measure operations and throughput related to file systems and mount targets. The available metrics help you determine quickly if your file system is accessible, how much data is flowing through its associated mount target, and if operations are producing unexpected errors. You can get visibility into your workload IOPs and latency, and set up alarms to receive notifications if tolerance thresholds are exceeded.

File Storage metrics include these resources:

  • File system: A high-performance shared storage entity made available to a network by an associated mount target.
  • Mount target: An NFS endpoint that lives in a VCN subnet of your choice and provides network access for file systems.

Metrics provided for file systems can be filtered or grouped by their associated mount target.

Raw Data Point Frequency

For every 1-minute interval, the File Storage service posts one raw data point to the Monitoring service. The Monitoring service charts show data points at 1-minute, 5-minute, 1-hour (60-minute), and 1-day intervals. Supported values for interval depend on the specified time range in the metric query (not applicable to alarm queries). More interval values are supported for smaller time ranges. For example, if you select one hour for the time range, then all interval values are supported. If you select 90 days for the time range, then only the 1h or 1d interval values are supported. The available statistics are calculated by using the count of 1-minute data points in the select interval. For example, for a given metric:

  • The mean for each 5-minute interval is calculated over 5 raw data points.
  • The mean for each 60-minute interval is calculated over 60 raw data points.

Required IAM Policy

To monitor resources, you must be given the required type of access in a policy  written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. The policy must give you access to the monitoring services as well as the resources being monitored. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which compartment  you should work in. For more information on user authorizations for monitoring, see the Authentication and Authorization section for the related service: Monitoring or Notifications.

Available Metrics: oci_filestorage

The metrics listed in the following table are automatically available for any file system or mount target. You do not need to enable monitoring on the resource to get these metrics.

You also can use the Monitoring service to create custom queries.

Each metric includes one or more of the following dimensions 
RESOURCEID
The OCID  of the file system or mount target.
MOUNTTARGETID
The OCID  of the mount target exporting an associated file system.
THROUGHPUT
The type of request throughput:
  • ReadThroughput
  • WriteThroughput
SIZE
The request size range:
  • 0-8 KiB
  • 8-64 KiB
  • 64 KiB - 1 MiB
HEALTHITEM
The type of health rate item:
  • SuccessRate
  • ErrorRate

File System Metrics

Metric Metric Display Name Unit Description Dimensions
FileSystemReadThroughput Read Throughput bytes Read throughput for the file system. If the file system is exported through multiple mount targets, total throughput for all mount targets is displayed. Expressed as bytes read per second.

resourceId

mountTargetId

throughput

FileSystemWriteThroughput Write Throughput bytes Write throughput for the file system. If the file system is exported through multiple mount targets, total throughput for all mount targets is displayed. Expressed as bytes written per second.
FileSystemReadRequestsbySize

Read

Requests

operation

 
Read requests by size: 0-8 KiB, 8-64 KiB, 64 KiB - 1 MiB. Expressed as operation per second, grouped by size. resourceId

mountTargetId

size

FileSystemWriteRequestsbySize

Write Requests

 
operation Write requests by size: 0-8 KiB, 8-64 KiB, 64 KiB - 1 MiB. Expressed as operation per second, grouped by size.
FileSystemReadAverageLatencybySize Read Latency second Read latency by size: 0-8 KiB, 8-64 KiB, 64 KiB - 1 MiB. Expressed as average read latency per second, grouped by size.
FileSystemWriteAverageLatencybySize Write Latency second Write latency by size: 0-8 KiB, 8-64 KiB, 64 KiB - 1 MiB. Expressed as average write latency per second, grouped by size.
MetadataRequestAverageLatency Metadata Latency second

Average metadata request latency for the following NFS operations: CREATE, GETATTR, SETATTR, ACCESS, LOOKUP, READLINK, and REMOVE. Expressed as average latency per second, grouped by operation.

resourceId

mountTargetId

operation

MetadataIOPS Metadata IOPs operation IOPs (Input/Output Operations Per Second) for the following NFS operations: CREATE, GETATTR, SETATTR, ACCESS, LOOKUP, READLINK, and REMOVE. Expressed as operations per second.
FileSystemUsage Usage bytes Total space utilization for a file system. Expressed as GiB consumed per second. resourceId

mountTargetId

Mount Target Metrics

Metric Metric Display Name Unit Description Dimensions
MountTargetReadThroughput

Read Throughput

 
bytes Read throughput for the mount target. If the mount target exports multiple file systems, total throughput for all file systems is displayed. Expressed as bytes read per interval.

resourceId

throughput

MountTargetWriteThroughput Write Throughput bytes Write throughput for the mount target. If the mount target exports multiple file systems, total throughput for all file systems is displayed. Expressed as bytes written per interval.
MountTargetConnections

Connections

 

count

 
Number of client connections for the mount target. Expressed as total connection count at the interval. resourceId
MountTargetHealth Health

percent

 
Number of successfully executed NFS API requests. Expressed as a percentage of total requests per interval. resourceId

healthItem

Tips for Working with File Storage Metrics

You can use the tables below to help interpret the data you see in File Storage metric charts. You can familiarize yourself with the typical metrics emitted by the File Storage service using the chart defaults.

File System Charts

This chart... shows this information... using these defaults.... that you can use to...

Read Throughput/

Write Throughput

The read or write throughput of your file system in bytes per second. Read/write throughput is averaged across all mount targets that export the file system. Only the default mean statistic is meaningful.

  • Statistic - mean
  • Interval - 1 minute
  • Time range - 3 hours
  • y-axis - bytes per second
  • Ensure that your workloads have sufficient read/write bandwidth for maximum performance.
  • Identify which file systems have the highest and lowest throughput.
  • Receive notifications when read or write throughput is above or below tolerance, so you can take action.

Read Requests/

Write Requests

Read or write operation requests processed by your file systems in bytes per second. Each operation is placed in one of these three size groups:

  • 0-8 KiB
  • 8-64 KiB
  • 64 KiB - 1 MiB

Only the default mean statistic is meaningful.

  • Statistic - mean
  • Interval - 1 minute
  • Time range - 3 hours
  • Grouped by: size
  • y-axis - bytes per second
  • See which file systems might have lower performance than expected.
  • Measure impact of operation size on file system and workload performance.
  • Identify and monitor file systems whose workloads are consistently receiving larger read or write requests and compare performance over time.
  • Receive notifications when operation bytes per second for a larger group size is too high.

Read Latency/

Write Latency

Average latency of read or write operation requests processed by your file systems in bytes per second. Each operation is placed in one of these three size groups:

  • 0-8 KiB
  • 8-64 KiB
  • 64 KiB - 1 MiB

These charts don't report zero latentcy, or periods when there are no read/write operations happening. Information is presented in the charts as individual data points.

     
  • Statistic - mean
  • Interval - 1 minute
  • Time range - 3 hours
  • Grouped by: size
  • See which file systems might have lower performance than expected due to operation latency.
  • Measure impact of operation latency on file system and workload performance.
  • Troubleshoot possible network or application issues that might increase file system latency.
  • Receive notifications when operation latency exceeds tolerance, so you can take action.
Metadata Latency

Average latency of read or write metadata operation requests processed by your file systems in bytes per second. CREATE, GETATTR, SETATTR, ACCESS, LOOKUP, READLINK, and REMOVE operations are shown.

Each operation is placed in one of these three size groups:

  • 0-8 KiB
  • 8-64 KiB
  • 64 KiB - 1 MiB
  • Statistic - mean
  • Interval - 1 minute
  • Time range - 3 hours
  • Grouped by: size
  • See which metadata operations requeststed by your workload have the highest and lowest latency.
  • Measure impact of metadata operation latency on file system and workload performance.
  • Receive notifications when a metadata operation exceeds tolerance.
  • Troubleshoot your application workloads.
Metadata IOPs

IOPs per second of read or write metadata operation requests processed by your file systems.CREATE, GETATTR, SETATTR, ACCESS, LOOKUP, READLINK, and REMOVE operations are shown.

  • Statistic - rate
  • Interval - 1 minute
  • Time range - 3 hours
  • Grouped by: operation
  • y-axis - bytes per second
  • See which metadata operations requested by your workload have the highest and lowest IOPs.
  • Identify specific operations that might consistently have higher or lower IOPs.
  • Receive notifications when IOPs for a metadata operation are below tolerance.
  • Troubleshoot your application workloads.
Usage

The total space utilization for each file system per hour. The data in this chart is presented differently than the utilization value shown in the Details tab of the file system:

  • File system utilization is displayed in GiB. This chart displays GB.
  • File system utilization is captured once every hour. This chart captures one data point every minute.
  • There may be temporary discrepancies between the file system utilization value and the Usage chart. For example, if the usage for a file system briefly spikes during the file system's hourly update, the utilization value may temporarily appear higher than expected when compared to the Usage chart.
 
  • Statistic - mean
  • Interval - 1 hour
  • Time range - 1 day
  • See what the total space utilization is for all of your file systems.
  • Identify which of your file systems are consuming the most and least space.
  • Identify which of your file systems are incurring the most and least cost.
  • Use in conjunction with the information in File System Usage and Metering and receive notifications when usage is not within expectations.

Mount Target Charts

This chart... shows this information... using these defaults.... that you can use to...

Read Throughput/

Write Throughput

The read or write throughput of your mount target in bytes per second. Read/write throughput is averaged across all file systems exported by the mount target. Only the default mean statistic is meaningful.

  • Statistic - mean
  • Interval - 1 minute
  • Time range - 3 hours
  • y-axis - bytes per second
  • Ensure that your workloads have sufficient read/write bandwidth for maximum performance.
  • Identify which mount targets have the highest and lowest throughput.
  • Receive notifications when read or write throughput is below tolerance, so you can take action.

Connections

The number of active connections for each mount target. Typically, one connection represents one NFS client.

  • Statistic - sum
  • Interval - 1 minute
  • Time range - 3 hours
  • See how many active connections each mount target has.
  • Measure impact of high connection count on file system and workload performance.
  • Decide if additional mount targets are required for your workload.

Health

The percentage of requests processed successfully by the mount target.

  • Statistic - mean
  • Interval - 1 minute
  • Time range - 3 hours
  • See which mount targets have the highest and lowest percentage of successfully processed requests.
  • Identify mount targets that are not performing well and troubleshoot possible causes.
  • Receive notifications when mount target health drops below tolerance, so you can take action.

Using the Console

To view default metric charts for a single file system
  1. Open the navigation menu. Under Core Infrastructure, click File Storage and then click File Systems.
  2. Click the file system to view its details.
  3. Under Resources, click Metrics.

For more information about monitoring metrics and using alarms, see Monitoring Overview. For information about notifications for alarms, see Notifications Overview.

To view default metric charts for a single mount target
  1. Open the navigation menu. Under Core Infrastructure, click File Storage and then click Mount Targets.

  2. Click the mount target to view its details.
  3. Under Resources, click Metrics.

For more information about monitoring metrics and using alarms, see Monitoring Overview. For information about notifications for alarms, see Notifications Overview.

To view default metric charts for multiple file systems and mount targets
  1. Open the navigation menu. Under Solutions and Platform, go to Monitoring and click Service Metrics.
  2. For Compartment, select the compartment that contains the file storage resource you're interested in.
  3. For Metric Namespace, select oci_filestorage.

    The Service Metrics page dynamically updates the page to show charts for each metric that is emitted by the selected metric namespace.

For more information about monitoring metrics and using alarms, see Monitoring Overview. For information about notifications for alarms, see Notifications Overview.