Monitor performance using the Oracle Cloud console

Observe and maintain the health of your OCI GoldenGate resources by regularly monitoring metrics, creating alarms, and subscribing to events to keep informed of any abnormal activity among your resources.

Related Topics

Metrics

In the Oracle Cloud console, you can view metrics on the deployment details page and the metrics explorer for any Extracts and Replicats marked as critical. You can also create alarms to stay informed of certain events and take action when needed.

Note:

Ensure that you upgrade your deployment to the latest version to leverage all available metrics. You must also select Critical to deployment health in the OCI GoldenGate deployment console for Extracts and Replicats for which to view metrics.

You can view the following OCI GoldenGate metrics in the Oracle Cloud console on the deployment details page and the metrics explorer for Extracts and Replicats marked as critical:

Data replication metrics:

  • CPU Utilization: The aggregate of all Oracle Compute Units (OCPUs).
  • CPU Consumption: The aggregate number of OCPUs consumed.
  • Memory Utilization: The percentage of aggregate memory. Each OCPUs allocates 16 GB memory.
  • Deployment Overall Health: The health score of the deployment, which is the aggregate health of the deployment's processes (Administration, Distribution, Receiver, and Performance Metric Services)
  • Deployment Inbound Lag: Lag captured for Extracts designated as critical. This metric is the aggregate of all Extracts in the deployment.
  • Deployment Outbound Lag: Lag captured for Replicats designated as critical. This metric is the aggregate of all Replicats in the deployment.
  • Swap Space Usage: Amount of swap space, in gigabytes, used by the deployment
  • Temp Space Usage: Amount of temporary space, in gigabytes, used by the deployment
  • File System Usage: Amount of file system space, in gigabytes, used by the deployment
  • Extract Status: Health percentage of an Extract process in the deployment.
  • Replicat Status: Health percentage of a Replicat process in the deployment.
  • Distribution Path Status: Health percentage of a Distribution Path process in the deployment.
  • Receiver Path Status: Health percentage of a Receiver Path process in the deployment.
  • Extract Lag: Average lag, in seconds, of a Extract process in the deployment.
  • Replicat Lag: Average lag of a Replicat, in seconds, of a Replicat process in the deployment.
  • Distribution Path Lag: Average lag, in seconds, of a Distribution Path process in the deployment.
  • Receiver Path Lag: Average lag, in seconds, of a Receiver Path process in the deployment.
  • Heartbeat Lag: Average lag of a Replicat, in seconds, from the source endpoint to the target endpoint.

Note:

You'll only see metrics for the processes used in your deployment. For example, if you only have an Extract and a Replicat, then you won't see Distribution or Receiver Path metrics.

Stream analytics metrics:

  • Pipeline Health: Overall health of a Stream Analytics pipeline.
  • Pipeline Processing Rate: Event processing rate of a Stream Analytics pipeline.
  • Pipeline Scheduling Delay: Stream Analytics pipeline microbatch scheduling delay.
  • Pipeline Total Delay: Stream Analytics pipeline microbatch total delay.
  • Pipeline Memory Usage: Stream Analytics pipeline memory usage by driver or executor.

Pipeline metrics:

  • CPU Utilization: The aggregate of all Oracle Compute Units (OCPUs).
  • Memory Utilization: The percentage of aggregate memory. Each OCPUs allocates 16 GB memory.
  • OCPU Consumption: The aggregate number of OCPUs consumed.
  • Pipeline Capture Status: Health percentage of a Capture (Extract) process.
  • Pipeline Apply Status: Health percentage of an Apply (Replicat) process.
  • Pipeline Capture Lag: Average lag, in seconds, of a Capture (Extract) process in the deployment.
  • Pipeline Apply Lag: Average lag, in seconds, of an Apply (Replicat) process in the deployment.
  • Pipeline Health: The health score of the pipeline's deployment, which is the aggregate health of the deployment's processes (Administration, Distribution, Receiver, and Performance Metric Services)
  • Heartbeat Lag: Average lag of an Apply process, in seconds, from the source endpoint to the target endpoint.

To learn more about about these metrics, see the OCI GoldenGate Metrics reference and Troubleshoot using the Oracle Cloud console.

Learn more about the Oracle Cloud Monitoring.

Create alarms

For each metric on the deployment details Monitoring page, you can create an alert to inform you when a condition is met. For example, you can create an alarm to notify you when OCPU consumption is less than 50%.

To create an alarm:
  1. From the Options dropdown of a metric chart, select Create an alarm on this query.
  2. On the Create alarm page, enter the Alarm name, and optionally an Alarm summary.
  3. Confirm the information populated in the Metric description and Metric dimension sections.
  4. For Trigger rule, complete the Operator, Value, and Trigger delay minutes fields. The graph displays the boundaries for which the alarm triggers a notification.
  5. For Defin alarm notifications, complete the fields as needed:
    • For Destination service, select Notifications.
    • For Compartment, select the compartment to store the topic used for this notification.
    • For Topic, click Create topic to set up a topic and subscription protocol in the designated compartment using the designated Destination service.
    • (Optional) Click + Additional destination service to add another destination service.
    • (Optional) Enable Repeat notification and select Notification frequency if you want the alarm to resend notifications at the specified intervals when the alarm is in the firing state.
    • (Optional) Enable Suppress notifications to specify a window of time to suspend evaluations and notifications. This is useful for maintenance periods.
  6. Click Save alarm.

For more information, see Viewing default metric charts.

Subscribe to Events

Events are structured messages that indicate changes in resources. Subscribing to OCI GoldenGate events enable you to keep informed of abnormal activity among your OCI GoldenGate resources, as well as when your deployment reaches its storage limit and when an upgrade is available.

Create rules to subscribe to these events and trigger actions. For example, a rule might specify goldengate.stateneedsattention triggers the Notifications service to send an email to your systems administrator.

For more information, see:

  • GoldenGate Events, for the full list of event types that you can create rules for.
  • Events Overview, to learn more about events, and how to create rules, and actions.