File
Due to the nature of container storage with layered and overlay filesystems, segmenting fs.*
metrics by container may return unexpected results and should be used with care. Typically they will report statistics of host filesystems mounted to the container, which can report duplication of metrics. They are not designed to report storage usage by container.
sysdig_fs_*
metrics are based on mounted filesystems for both hosts and containers, and are generated for each filesystem.sysdig_host_fs_*
and sysdig_container_fs_*
are nothing but sum aggregates of mounted filesystems on host and container respectively.- File systems in containers are filtered out based on
!(“tmpfs".equals(device) || mountDir.startsWith("/sys/fs/cgroup") || mountDir.startsWith("/proc/") || mountDir.contains("/secrets") || mountDir.startsWith("/etc") || device.startsWith("overlay”))
. However, they seem to be included in the aggregated sysdig_container_fs_*
metrics. sysdig_fs_*
metrics have the same name for both host and container file systems and therefore use a filter to view individual types.- To view only host filesystems, apply the
{container_id = ‘’}
filter. - To view only the file systems mounted to containers, apply the
{container_id !=‘’
condition.
sysdig_filestats_host_file_error_total_count
| |
---|
Prometheus ID | sysdig_filestats_host_file_error_total_count |
Legacy ID | file.error.total.count |
Metric Type | counter |
Unit | number |
Description | Number of error caused by file access. |
Additional Notes | By default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI. |
sysdig_filestats_host_file_in_bytes
| |
---|
Prometheus ID | sysdig_filestats_host_file_in_bytes |
Legacy ID | file.bytes.in |
Metric Type | counter |
Unit | data |
Description | Amount of bytes read from file. |
Additional Notes | By default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI. |
sysdig_filestats_host_file_open_count
| |
---|
Prometheus ID | sysdig_filestats_host_file_open_count |
Legacy ID | file.open.count |
Metric Type | counter |
Unit | number |
Description | When segmenting by file name, the metric represents the rate of open events for a particular file With other segmentations, it represents the number of all files currently open in a particular context (host, container, process, etc.). |
Additional Notes | |
sysdig_filestats_host_file_out_bytes
| |
---|
Prometheus ID | sysdig_filestats_host_file_out_bytes |
Legacy ID | file.bytes.out |
Metric Type | counter |
Unit | data |
Description | Amount of bytes written to file. |
Additional Notes | By default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI. |
sysdig_filestats_host_file_total_bytes
| |
---|
Prometheus ID | sysdig_filestats_host_file_total_bytes |
Legacy ID | file.bytes.total |
Metric Type | counter |
Unit | data |
Description | Amount of bytes read from and written to file. |
Additional Notes | By default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI. |
sysdig_filestats_host_file_total_time
| |
---|
Prometheus ID | sysdig_filestats_host_file_total_time |
Legacy ID | file.time.total |
Metric Type | counter |
Unit | time |
Description | Time spent in file I/O. |
Additional Notes | By default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI. |
sysdig_fs_free_bytes
| |
---|
Prometheus ID | sysdig_fs_free_bytes |
Legacy ID | fs.bytes.free |
Metric Type | gauge |
Unit | data |
Description | Filesystem available space. |
Additional Notes | |
sysdig_fs_free_percent
| |
---|
Prometheus ID | sysdig_fs_free_percent |
Legacy ID | fs.free.percent |
Metric Type | gauge |
Unit | percent |
Description | Percentage of filesystem free space. |
Additional Notes | |
sysdig_fs_inodes_total_count
| |
---|
Prometheus ID | sysdig_fs_inodes_total_count |
Legacy ID | fs.inodes.total.count |
Metric Type | gauge |
Unit | number |
Description | |
Additional Notes | |
sysdig_fs_inodes_used_count
| |
---|
Prometheus ID | sysdig_fs_inodes_used_count |
Legacy ID | fs.inodes.used.count |
Metric Type | gauge |
Unit | number |
Description | |
Additional Notes | |
sysdig_fs_inodes_used_percent
| |
---|
Prometheus ID | sysdig_fs_inodes_used_percent |
Legacy ID | fs.inodes.used.percent |
Metric Type | gauge |
Unit | percent |
Description | |
Additional Notes | |
sysdig_fs_total_bytes
| |
---|
Prometheus ID | sysdig_fs_total_bytes |
Legacy ID | fs.bytes.total |
Metric Type | gauge |
Unit | data |
Description | Filesystem size. |
Additional Notes | |
sysdig_fs_used_bytes
| |
---|
Prometheus ID | sysdig_fs_used_bytes |
Legacy ID | fs.bytes.used |
Metric Type | gauge |
Unit | data |
Description | Filesystem used space. |
Additional Notes | |
sysdig_fs_used_percent
| |
---|
Prometheus ID | sysdig_fs_used_percent |
Legacy ID | fs.used.percent |
Metric Type | gauge |
Unit | percent |
Description | Percentage of the sum of all filesystems in use. |
Additional Notes | |