Learn about ONTAP performance counter mapping
ONTAP maintains detailed performance information about the ONTAP cluster, including the physical and logical components of the system. This information is provided through a collection of performance counters. You can retrieve these counters to identify performance issues and improve the overall operation of your cluster.
The ONTAP REST API provides access to the counters through a series of tables while the earlier ONTAPI uses an object organization instead. Each of the tables in the REST API includes a description of the performance counters as well as how they map to the equivalent ONTAPI objects. You can use these tables to assist with the migration of your automation code from ONTAPI to the ONTAP REST API.
There are additional resources available to help you migrate your automation code to the ONTAP REST API. Use the following documentation to learn more about ONTAP performance counters and the benefits of migrating your ONTAPI automation code to the ONTAP REST API.
Transition from objects to tables
The ONTAPI API, also referred to as the Zephyr API (ZAPI), is available through the NetApp Manageability SDK. ONTAPI presents the ONTAP performance data as a collection of objects, each with a set of counter properties. The REST API provides the equivalent data in a table format for a subset of the ONTAPI objects. Navigation begins in the sidebar with a list of the performance counter tables that are accessible through the REST API.
Consistent description of each table
The description of every table is based on a consistent format. After a brief introduction and an indication of the related ONTAPI object, the following sections are included.
-
Table row IDs
Each counter table is accessed through a unique ID. This section provides a list of the one or more ID formats supported for the table.
-
Properties
This section includes the names of the ONTAPI string counters and the equivalent REST property for each.
-
Counters
There is also a mapping from the numeric ONTAPI counters to the equivalent REST counters.
-
Content changes
Any changes from the ONTAPI string counters to the respective REST properties are described here.
-
Table aliases
This section includes a description of any aliases for the aggregated tables.