Monitor Metrics for VM Cluster Resources
You can monitor the health, capacity, and performance of your VM clusters and databases with metrics, alarms, and notifications. You can use Oracle Cloud Infrastructure Console, Monitoring APIs, or Database Management APIs to view metrics.
To view metrics you must have the required access as specified in an Oracle Cloud Infrastructure policy (whether you're using the Console, the REST API, or another tool). For more information on policies, see Getting Started with Policies.
- Prerequisites for Using Metrics
The following prerequisites must be met for the metrics to flow out of the VM Cluster. - View Metrics for a VM Cluster
To view the metrics for Guest VMs using the console, use this procedure. - View Metrics for a Database
To view the metrics for a database using the console, use this procedure. - View Metrics for VM Clusters in a Compartment
To view the metrics for databases in a compartment using the console, use this procedure. - View Metrics for Databases in a Compartment
To view the metrics for databases in a compartment using the console, use this procedure. - Manage Oracle Trace File Analyzer
Related Topics
Prerequisites for Using Metrics
The following prerequisites must be met for the metrics to flow out of the VM Cluster.
- Metrics on the VM Clusters depend on the Oracle Trace File Analyzer (TFA) agent. Ensure that this component is up and running. AHF version 23.2.0 or higher is required for capturing metrics from the VM Clusters. To start, stop, or check the status of TFA, see Manage Oracle Trace File Analyzer.
- To view the metrics on the Oracle Cloud Infrastructure Console, the TFA flag
defaultocimonitoring
must be set to ON. This flag is set to ON by default and you need not perform any action to set this. If you are not seeing metrics on the Console, then asroot
user on the guest VM, check if the flag is set to ON.tfactl get defaultocimonitoring .---------------------------------------------------------------------. | <host name> | +-------------------------------------------------------------+-------+ | Configuration Parameter | Value | +-------------------------------------------------------------+-------+ | Send CEF metrics to OCI Monitoring ( defaultOciMonitoring ) | ON | '-------------------------------------------------------------+-------'
If thedefaultocimonitoring
flag is set to OFF, then run thetfactl set defaultocimonitoring=on
ortfactl set defaultocimonitoring=ON
command to turn it on:tfactl set defaultocimonitoring=on Successfully set defaultOciMonitoring=ON .---------------------------------------------------------------------. | <host name> | +-------------------------------------------------------------+-------+ | Configuration Parameter | Value | +-------------------------------------------------------------+-------+ | Send CEF metrics to OCI Monitoring ( defaultOciMonitoring ) | ON | '-------------------------------------------------------------+-------'
- The network communication uses the existing path that the Control Plane Server uses to reach the OCI Services. For more information, see Network Requirements for Oracle Exadata Database Service on Cloud@Customer.
View Metrics for a VM Cluster
To view the metrics for Guest VMs using the console, use this procedure.
When there is a network problem and Oracle Trace File Analyzer (TFA) is unable to post metrics, TFA will wait for one hour before attempting to retry posting the metrics. This is required to avoid creating a backlog of metrics processing on TFA.
Potentially one hour of metrics will be lost between network restore and the first metric posted.
Related Topics
Parent topic: Monitor Metrics for VM Cluster Resources
View Metrics for a Database
To view the metrics for a database using the console, use this procedure.
When there is a network problem and Oracle Trace File Analyzer (TFA) is unable to post metrics, TFA will wait for one hour before attempting to retry posting the metrics. This is required to avoid creating a backlog of metrics processing on TFA.
Potentially one hour of metrics will be lost between network restore and the first metric posted.
Related Topics
Parent topic: Monitor Metrics for VM Cluster Resources
View Metrics for VM Clusters in a Compartment
To view the metrics for databases in a compartment using the console, use this procedure.
When there is a network problem and Oracle Trace File Analyzer (TFA) is unable to post metrics, TFA will wait for one hour before attempting to retry posting the metrics. This is required to avoid creating a backlog of metrics processing on TFA.
Potentially one hour of metrics will be lost between network restore and the first metric posted.
Related Topics
Parent topic: Monitor Metrics for VM Cluster Resources
View Metrics for Databases in a Compartment
To view the metrics for databases in a compartment using the console, use this procedure.
When there is a network problem and Oracle Trace File Analyzer (TFA) is unable to post metrics, TFA will wait for one hour before attempting to retry posting the metrics. This is required to avoid creating a backlog of metrics processing on TFA.
Potentially one hour of metrics will be lost between network restore and the first metric posted.
Related Topics
Parent topic: Monitor Metrics for VM Cluster Resources
Manage Oracle Trace File Analyzer
The deployment of the cloud-certified Autonomous Health Framework (AHF), which includes Oracle Trace File Analyzer, is managed by Oracle. You shouldn’t install this manually on the guest VMs.
- To check the run status of Oracle Trace File Analyzer, run the
tfactl status
command asroot
or a non-root user:# tfactl status .-------------------------------------------------------------------------------------------------. | Host | Status of TFA | PID | Port | Version | Build ID | Inventory Status| +----------------+---------------+--------+------+------------+----------------------+------------+ | node1 | RUNNING | 41312 | 5000 | 22.1.0.0.0 | 22100020220310214615| COMPLETE | | node2 | RUNNING | 272300 | 5000 | 22.1.0.0.0 | 22100020220310214615| COMPLETE | '----------------+---------------+--------+------+------------+----------------------+------------'
-
To start the Oracle Trace File Analyzer daemon on the local node, run the
tfactl start
command asroot
:# tfactl start Starting TFA.. Waiting up to 100 seconds for TFA to be started.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Successfully started TFA Process.. . . . . . TFA Started and listening for commands
- To stop the Oracle Trace File Analyzer daemon on the local node, run the
tfactl stop
command asroot
:# tfactl stop Stopping TFA from the Command Line Nothing to do ! Please wait while TFA stops Please wait while TFA stops TFA-00002 Oracle Trace File Analyzer (TFA) is not running TFA Stopped Successfully Successfully stopped TFA..
Parent topic: Monitor Metrics for VM Cluster Resources