Oracle Cloud Infrastructure GoldenGate Metrics

Monitor the deployment health, capacity, and overall performance of your Oracle Cloud Infrastructure GoldenGate deployments using metrics, alarms, and notifications. In the Oracle Cloud console, you can monitor metrics on the OCI GoldenGate deployment details page or using the Metrics Explorer.

Resources: goldengate-deployments, goldengate-connections

Overview

Oracle Cloud Infrastructure GoldenGate metrics help you measure the amount of data replicated between source and target databases.

The following terms are helpful for understanding metrics:

Namespace: A container for Oracle Cloud Infrastructure GoldenGate metrics. The namespace for Oracle Cloud Infrastructure GoldenGate is oci_goldengate.
Metrics: The fundamental concept in telemetry and monitoring. Metrics define a time-series set of datapoints. Each metric is uniquely defined by namespace, metric name, compartment identifier, a set of one or more dimensions, and a unit of measure. Each datapoint has a timestamp, a value, and a count associated with it.
Dimensions: A key-value pair that defines the characteristics associated with the metric. For example, resourceId, which is the Oracle Cloud Infrastructure GoldenGate deployment OCID.
Statistics: Metric data aggregations over specified periods of time. Aggregations are done using the namespace, metric name, dimensions, and the datapoint unit of measure within the time period specified.
Alarms: Used to automate operations monitoring and performance. An alarm keeps track of changes that occur over a specific period of time. It also performs one or more defined actions, based on the rules defined for the metric.

Prerequisites

IAM policies: To monitor resources, you must be given the required type of access in a policy written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. The policy must give you access to the monitoring services as well as the resources being monitored. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which compartment you should work in. For more information on user authorizations for monitoring, see Monitoring or Notifications.
The metrics listed on this page are automatically available for any Oracle Cloud Infrastructure GoldenGate deployment you create. You do not need to enable monitoring on the resource to get these metrics.

Available Metrics

Note

Ensure that you upgrade your deployment to the latest version to leverage all available metrics.

Oracle Cloud Infrastructure GoldenGate metrics may include the following dimensions:

deploymentId: For all metrics, the deploymentId is the deployment OCID.
deploymentName: Name of the Oracle Cloud Infrastructure GoldenGate deployment.
ExtractName: Name of an Extract process in the Oracle Cloud Infrastructure GoldenGate deployment.
ReplicatName: Name of a Replicat process in the Oracle Cloud Infrastructure GoldenGate deployment.
DistributionPathName: Name of a Distribution Path process in the Oracle Cloud Infrastructure GoldenGate deployment.
ReceiverPathName: Name of a Receiver Path process in the Oracle Cloud Infrastructure GoldenGate deployment.
component: Pipeline runtime process, either driver or executor.

Metric	Metric Description	Metric Dimensions	Recommended Actions
Name: `CpuUtilization` Display Name: CPU Utilization	Total CPU usage percentage by all consumer groups. Check the CPU Utilization when: The OCI GoldenGate deployment console is slow or not responsive There is an Extract or Replicat lag	`deploymentId` `deploymentName`	If CPU Utilization is high, you can: Add OCPUs to your deployment Enable Autoscale, if not already enabled Check storage utilization and trail size, and purge trail files if high
Name: `OcpuConsumption` Display Name: OCPU Consumption	Total number of OCPUs used by the deployment. When the count is lower than the minimum number of OCPUs, the minimum is shown. When the number of OCPUs is greater than the minimum number, the actual number of OCPUs used is shown.	`deploymentId` `deploymentName`	If OPCU Consumption is high, you can: Add OCPUs to your deployment Enable Autoscale, if not already enabled
Name: `MemoryUtilization` Display Name: Memory Utilization	Percentage of available memory used. The need for memory is aligned with the size of the data replicated. If enough memory is allocated, then each open transaction is kept in memory until a commit record is received.	`deploymentId` `deploymentName`	If Memory Utilization is high, you can: Add OCPUs to your deployment Enable Autoscale, if not already enabled
Name: `DeploymentHealth` Display Name: Overall Deployment Health	Overall percentage health of deployment services. There are four services: Administration service, Distribution service, Receiver service, and Performance Metric service. If all four are running healthy, the expected score is 100%. If Deployment Health is 50%, then only two of the services are running healthy.	`deploymentId` `deploymentName`	When you create Extract, Replicat, Distribution or Receiver Paths, you can mark the process as Critical to Deployment Health under Managed Options. If the Deployment Health is >100%, then check the processes marked as Critical to Deployment Health.
Name: `DeploymentInboundLag` Display Name: Deployment Inbound Lag	Average lag, in seconds, for all inbound streams critical to deployment health	`deploymentId` `deploymentName`	Not applicable
Name: `DeploymentOutboundLag` Display Name: Deployment Outbound Lag	Average lag, in seconds, for all outbound streams critical to deployment health	`deploymentId` `deploymentName`	Not applicable
Name: `SwapSpaceUsage` Display Name: Swap Space Usage	Percentage of Swap Space used by the deployment. As OCI GoldenGate only writes only committed transaction to the trail files, all the uncommitted transactions are cached in memory. Cache uses both physical memory and swap space (virtual memory). Swap space is located on hard drives to provide additional memory when the physical memory (RAM) is full.	`deploymentId` `deploymentName`	If Swap Space Usage is increasing, consider adding additional OCPUs to the deployment to increase physical memory (RAM).
Name: `TempSpaceUsage` Display Name: Temporary Space Usage	Percentage of temporary space used by the deployment. When total cached transaction data exceeds the Cachesize setting, Extract writes cache data to temporary files. It is more efficient for the operating system to swap to disk than it is for Extract to write temporary files.	`deploymentId` `deploymentName`	If Temp Space Usage is increasing, consider adding additional OCPUs to the deployment to increase physical memory (RAM).
Name: `FileSystemUsage` Display Name:	Percentage of File System Space used by the deployment	`deploymentId` `deploymentName`	If File System Usage is high: Check trail file size and purge unnecessary trail files Check Temp Space Usage to see if OCI GoldenGate ran short of physical memory (RAM)
Name: `ExtractStatus` Display Name: Extract Status	Health percentage of an Extract process in the deployment 100% when process is Running 0% when process is Abended or Stopped	`deploymentId` `deploymentName` `ExtractName`	If an Extract processes is abended or stopped, check the report file for the root cause or error to troubleshoot the issue.
Name: `ReplicatStatus` Display Name: Replicat Status	Health percentage of a Replicat process in the deployment 100% when process is Running 0% when process is Abended or Stopped	`deploymentId` `deploymentName` `ReplicatName`	If a Replicat is stopped or abended, then check the Replicat report file for the root cause or error to diagnose issues.
Name: `DistributionPathStatus` Display Name: Distribution Path Status	Health percentage of a Distribution Path process in the deployment 100% when process is Running 0% when process is Abended or Stopped	`deploymentId` `deploymentName` `DistributionPathName`	If abended or stopped, then possible causes are: Change in credentials Receiver service stopped Target deployment stopped
Name: `ReceiverPathStatus` Display Name: Receiver Path Status	Health percentage of a Receiver Path process in the deployment 100% when process is Running 0% when process is Abended or Stopped	`deploymentId` `deploymentName` `ReceiverPathName`	If the Receiver Path Status is stopped or abended: Check for changes in credentials Check the target deployment health Check for network issues between the source and target deployments
Name: `ExtractLag` Display Name: Extract Lag	The difference, in seconds, between the time the Extract processed a record (based on the system clock) and the time stamp of that record in the data source.	`deploymentId` `deploymentName` `ExtractName`	If the Extract Lag is high, then: Check CPU Utilization to see if the deployment ran out of resources Check Memory Utilization to see if the assigned resources can handle the Extract size If the data source is an on-premises database, check network health and latency Check for performance issues with the source database Check file system storage
Name: `ReplicatLag` Display Name: Replicat Lag	The difference, in seconds, between the time the Replicat processed the last record (based on the system clock) and the time stamp of the record in the trail.	`deploymentId` `deploymentName` `ReplicatName`	If the Replicat Lag is high: Check CPU and Memory Utilization to see if the deployment ran out of resources Check Extract Lag for any latency issues Check the Distribution Path Lab for latency issues Check network latency between OCI GoldenGate and the target database. Recommended round trip ping is 5ms or less. HANDLECOLLISIONS can cause performance issues and not recommended for Change Data Capture (CDC) replication
Name: `DistributionPathLag` Display Name: Distribution Path Lag	Average lag, in seconds, of a Distribution Path process in the deployment. For example, if the source and target deployments are running in two different data centers, network latency issues could impact lag.	`deploymentId` `deploymentName` `DistributionPathName`	Not applicable
Name: `ReceiverPathLag` Display Name: Receiver Path Lag	Average lag, in seconds, of Receiver Path process in the deployment	`deploymentId` `deploymentName` `ReceiverPathName`	Not applicable
Name: `HeartbeatLag` Display Name: Heartbeat Lag	Replication lag, in seconds, from the source endpoint to the target endpoint.	`ReplicatName` `deploymentName` `deploymentId` `ageSeconds`	If the Heartbeat Lag is high, then: Check CPU Utilization to see if the deployment ran out of resources Check Memory Utilization to see if the assigned resources can handle the Extract size If the data source is an on-premises database, check network health and latency Check for performance issues with the source database Check file system storage Check Extract Lag for any latency issues Check the Distribution Path Lab for latency issues Check network latency between OCI GoldenGate and the target database. Recommended round trip ping is 5ms or less. HANDLECOLLISIONS can cause performance issues and not recommended for Change Data Capture (CDC) replication
Name: `PipelineHealth` Display Name: Pipeline Health	Overall health percentage of a Stream Analytics pipeline. 100% when a pipeline is healthy during the time range. 0% when the pipeline is unhealthy or not running during the time range. Between 0% to 100% when a pipeline was unhealthy and is recovering or going to terminate within the time range and needs attention.	`deploymentId` `deploymentName` `PipelineName`	Not applicable
Name: `PipelineProcessingRate` Display Name: Pipeline Processing Rate	Average number of events processed per second by pipelines in the deployment.	`deploymentId` `deploymentName` `PipelineName`	Not applicable
Name: `PipelineSchedulingDelay` Display Name: Pipeline Scheduling Delay	Average scheduling delay in milliseconds (ms) of pipelines in the deployment.	`deploymentId` `deploymentName` `PipelineName`	Not applicable
Name: `PipelineTotalDelay` Display Name: Pipeline Total Delay	Average total delay in milliseconds (ms) of pipelines in the deployment.	`deploymentId` `deploymentName` `PipelineName`	Not applicable
Name: `PipelineMemoryUsage` Display Name: Pipeline Memory Usage	Memory usage in megabytes (MB) of pipeline drivers and executors in the deployment.	`deploymentId` `deploymentName` `PipelineName` `component`	Not applicable

Using the Console

To view Oracle Cloud Infrastructure GoldenGate metrics:

In the Console navigation menu, under Solutions and Platform, go to Monitoring and then select Service Metrics.
For Compartment, select the compartment that contains the Oracle Cloud Infrastructure GoldenGate deployments you're interested in.
For Metric Namespace, select oci_goldengate.

Refresh your browser to view the latest metrics emitted by the service.

Oracle Cloud Infrastructure Documentation