ITM Agent Insights: New attributes in the 6.30 FP5 Unix Disk Group for ZFS metrics

Body

In this blog, I will list the ten new attributes introduced in the 6.30 FP5 Monitoring Agent for Unix OS on Solaris to monitor the ZFS in the Unix Disk group.

The first eight attributes show ZFS properties, the last two attributes introduce a new calculation for the space used percent that corresponds to the output of the command "df -h".

Below are the new attributes' complete list and their descriptions.

Ten new attributes added to the Unix Disk attribute group:

1. ZFS Quota (KBytes)
The ZFS property QUOTA that limits the amount of disk space that a dataset and its descendants can consume.

Note: the value -1 indicates Not Available, -2 indicates Not Collected, 9,223,372,036,854,775,807 indicates Value_Exceeds_Maximum, and -9,223,372,036,854,775,808 indicates Value_Exceeds_Minimum.

2. ZFS RefQuota (KBytes)
The ZFS property REFQUOTA that sets the amount of disk space that a dataset can consume.

Note: the value -1 indicates Not Available, -2 indicates Not Collected, 9,223,372,036,854,775,807 indicates Value_Exceeds_Maximum, and -9,223,372,036,854,775,808 indicates Value_Exceeds_Minimum.

3. ZFS Reservation (KBytes)

The ZFS property RESERVATION that sets the amount of reserved space guaranteed to a dataset and its descendants.

Note: the value -1 indicates Not Available, -2 indicates Not Collected, 9,223,372,036,854,775,807 indicates Value_Exceeds_Maximum, and -9,223,372,036,854,775,808 indicates Value_Exceeds_Minimum.

4. ZFS RefReservation (KBytes)
The ZFS property REFRESERVATION that sets the amount of reserved space guaranteed to a dataset.

Note: the value -1 indicates Not Available, -2 indicates Not Collected, 9,223,372,036,854,775,807 indicates Value_Exceeds_Maximum, and -9,223,372,036,854,775,808 indicates Value_Exceeds_Minimum.

5. ZFS Used by Dataset (KBytes)
The ZFS property USEDBYDATASET that shows the amount of space used by a dataset.

Note: the value -1 indicates Not Available, -2 indicates Not Collected, 9,223,372,036,854,775,807 indicates Value_Exceeds_Maximum, and -9,223,372,036,854,775,808 indicates Value_Exceeds_Minimum.

6. ZFS Used by Children (KBytes)
The ZFS property USEDBYCHILDREN that shows the amount of space used by the children of a dataset.

Note: the value -1 indicates Not Available, -2 indicates Not Collected, 9,223,372,036,854,775,807 indicates Value_Exceeds_Maximum, and -9,223,372,036,854,775,808 indicates Value_Exceeds_Minimum.

7. ZFS Used by Snapshots (KBytes)
The ZFS property USEDBYSNAPSHOTS that shows the amount of space used by the snapshots of a dataset.

Note: the value -1 indicates Not Available, -2 indicates Not Collected, 9,223,372,036,854,775,807 indicates Value_Exceeds_Maximum, and -9,223,372,036,854,775,808 indicates Value_Exceeds_Minimum.

8. ZFS Used by RefReservation\(KBytes)
The ZFS property USEDBYREFRESERVATION that shows the amount of space guaranteed for a dataset.

Note: the value -1 indicates Not Available, -2 indicates Not Collected, 9,223,372,036,854,775,807 indicates Value_Exceeds_Maximum, and -9,223,372,036,854,775,808 indicates Value_Exceeds_Minimum.

9. ZFS Space Used (KBytes)
The amount of space used in the dataset total size, expressed in kilobytes and calculated as the difference between the size and the space available. Because space is shared within a pool, the total space used will include also the possible part of space used by other datasets in the dataset total size.

Note: the value -1 indicates Not Available, -2 indicates Not Collected, 9,223,372,036,854,775,807 indicates Value_Exceeds_Maximum, and -9,223,372,036,854,775,808 indicates Value_Exceeds_Minimum.

10. ZFS Space Used Percent
The complementary of Space Available Percent, it is calculated as 100 - Space Available Percent. In this percentage all the busy space is considered, even if this space is not all used by this specific dataset.
Valid entries are whole numbers up to 100, such as 65 for 65%. Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Note: The new attributes are not visible in the default queries for the TEP workspaces as they are specific of Solaris systems and ZFS. A new query should be created (or an existing one modified) to add the new attributes to the TEP workspace.

Additional ITM Agent Insights series of IBM Tivoli Monitoring Agent blogs are indexed under ITM Agent Insights: Introduction.

Subscribe and follow us for all the latest information directly on your social feeds: