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:

  • 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.
  • DistributionPathStatus: Health percentage of a Distribution Path process in the deployment.
  • ReceiverPathStatus: Health percentage of a Receiver Path process in the deployment.
  • ExtractLag: Average lag, in seconds, of a Extract process in the deployment.
  • ReplicatLag: Average lag, in seconds, of a Replicat process in the deployment.
  • DistributionPathLag: Average lag, in seconds, of a Distribution Path process in the deployment.
  • ReceiverPathLag: Average lag, in seconds, of a Receiver Path process in the deployment.
  • HeartbeatLag: Average lag, in minutes, of a Heartbeat process in the deployment.

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.

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 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, under Define Alarm, add the trigger.
  3. For Alarm Settings, complete the following fields as needed:
    • Alarm Name: Enter the name that serves as the title for notifications related to this alarm. Avoid entering confidential information.
    • Alarm Severity: Select the perceived type of response required when the alarm is in the firing state.
    • Alarm Body: Enter the content of the notification to deliver.
    • Tags (optional): Select or enter free-form tags to apply to this resource.
    • Metric description: The metric to evaluate for the alarm condition.
      • Compartment: Select the compartment that contains the resources that emit the metrics evaluated by the alarm. The selected compartment is also where the alarm is stored.
      • Metric Namespace: Enter the service or application emitting metrics for the resources that you want to monitor.
      • Resource Group (optional): Select the group that the metric belongs to.
      • Metric Name: Enter the name of the metric. Only one metric can be specified.
      • Interval: Select the aggregation window, or the frequency at which data points are aggregated.
      • Statistic: Select the aggregate function.
  4. Confirm the values for Metric dimensions. Optionally, click + Additional dimension to add another dimension to the alarm.
  5. For Trigger rule, complete the Operator, Value, and Trigger delay minutes fields. The graph displays the boundaries for which the alarm triggers a notification.
  6. For Notifications, complete the fields as needed:
    • For Destination service, select Notifications Service.
    • 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 Interval 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.
  7. 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.