A . YOU query VSSYSTEM_EVENTS and filter for the event 'cell physical IO interconnect bytes returned by smart scan', associated to your table. This does not show how much data was filtered by Smart Scan, but only how much data was returned after Smart Scan12.
. You query v$SYSTAT and filter for the statistic 'cell smart table scan', associated to your table. This does not show how much data was filtered by Smart Scan for a specific table, but only for all tables in a session12.
https://www.databasejournal.com/oracle/monitoring-smart-scans-in-oracle-exadata/

According to the Oracle documentation1, two monitoring tools that might be useful in examining I/O performance for the prod database are:
cellcli (or exacli/exadcli) to examine storage server metrics such as database, category, ceiidisk, and griddisk (D). This tool can help you monitor the I/O Resource Management (IORM) metrics and identify any bottlenecks or imbalances in the storage layer.
I/O-specific dynamic performance views such as v$iostat_fiie, v$iostat_function, and v$iostat_consumer_group from the prod database instances using SQL *p1us . These views can help you monitor the I/O activity and latency at the file, function, and consumer group level.

Oracle KVM Guest, Oracle Enterprise Manager Agent (OMA), RDBMS instance, Automatic Diagnostic Repository Command Interpreter (ADRCI), CELLCLI, diskmon, and Restart Server (RS) can all run on the database servers. The Cell Server (CELLSRV) and Management Server (MS) can both run on the Exadata storage servers. Specific instructions for installing and configuring these software components can be found in the book and can be referenced here: https://docs.oracle.com/cd/E80920_01/E80920/html/x9m_software_components.html.