Oracle Cloud Infrastructure

This extension monitors basics of the Oracle Cloud Infrastructure.

This is intended for users, who:
Want to monitor foundation of their Oracle Cloud Infrastructure, including:

• Compute resources
• Cloud networking resources
• Site-to-Site VPN
• Load Balancing
• Block storage
• Object storage
• Filesystem storage
• API gateway
• OCI serverless functions

This extension does not cover every single service available on Oracle Cloud.
This extension focuses on basic Oracle Cloud Infrastructure services and does not look to monitor Oracle SaaS offerings like e.g. CX, HCM, ERP, SCM, EPM and alike.

This extension enables you to:

• Monitor health and performance of the Oracle Cloud Infrastructure
• focusing on compute, storage and networking foundation of the infrastructure.

This extension is executed by the ActiveGate (remote monitoring). You need to have an ActiveGate provisioned in your environment and networking set up so the ActiveGate can connect to the subject OCI tenant you are about to monitor.

To start, activate the extension in your environment using the in-product Hub. Then provide your OCI monitoring endpoint whereabouts. You will need to provide:

• Compartment ID
• Tenancy
• User
• Fingerprint
• Region
• Path location of a PEM key file which extension will use to sign OCI monitoring API requests

for each endpoint you are about to monitor on your OCI.

Note: Because the configuration requires the Compartment ID & region, a new endpoint or monitoring configuration will need to be created to monitor a new region or compartment. The User account provided in the configuration must also have permissions to read all OCI settings & resources.

The PEM key file will need to be placed on any ActiveGate that is running the extension, in a location that is accessible to the extension. The recommended default location for the PEM file is:

• Linux:

  <CONFIG>/remotepluginmodule/agent/conf/certificates/
  (default: /var/lib/dynatrace/remotepluginmodule/agent/conf/certificates/)
  

• Windows:

  %PROGRAMDATA%\dynatrace\remotepluginmodule\agent\conf\certificates
  

Refer to Oracle documentation for details on how to set up the monitoring endpoint access:

• OCI API concepts
• API signing key handling
• Overview of OCI monitoring

Import Tags

To import tags from OCI, two additional configuration options are required:

• Dynatrace environment ID
• API Token with Entities.Read and Entities.Write scopes.

Refer to the documentation for creating an API token with the correct scopes.

This extension is built on top of the Extension Framework 2.0 and delivers:

• Metrics retrieved from the OCI APIs (extension internally uses Python to connect to the OCI APIs)
• A Dashboard
• Topology definitions
• Unified Analysis screens

Metrics collected:

• Compute resources usage and performance
• Load balancers and network load balancers usage and performance
• Virtual cloud networks usage and performance
• Site-to-Site VPN usage and performance
• Block storage volumes usage and performance
• Object storage volumes usage and performance
• Filesystem storage volumes usage and performance
• API gateway usage and performance
• Serverless OCI functions usage, performance and errors

• OCI API access from ActiveGate is required

Q: What OCI API endpoints is this extension connecting to?

A: OCI performance counters are available though a number of different endpoints, whose specific URLs reflect specific monitored services and regions in whcich those services run. Oracle published the list of API reference endpoints here.

None of these URLs needs to be provided in the extension configuration. Oracle SDK builds those URLs using input the extension requires (Compartment ID, Tenancy, Region) and specific service it monitors (compute, load balancer, VCN, VPN and so on - they are listed above). Oracle SDK libraries are embedded in this extension distribution.

Q: What is the DDU Consumption of this extension?

A: The formula for DDU consumption of the extension will be published at a later date. For now, when estimating consumption of this Preview version of the extension, take into account the numbers of:

10 metrics per cloud:oci:compute_instance
 4 metrics per cloud:oci:instance_pool
27 metrics per cloud:oci:load_balancer
 9 metrics per cloud:oci:network_load_balancer
12 metrics per cloud:oci:vcn
 6 metrics per cloud:oci:vpn
 5 metrics per cloud:oci:block_volume
10 metrics per cloud:oci:file_system
 2 metrics per cloud:oci:object_store
12 metrics per cloud:oci:api_gateway
 2 metrics per cloud:oci:function

and aggregate these for all OCI tenants you plan to monitor. This way you arrive at the number of metric points that monitoring will bring every monitoring interval.

Metric to DDU consumption multiplier is:

number of metrics * 525.6 DDUs/year

DDU cost above does not include any possible Log events or Custom events triggered by the extension. For more information on this, please visit the DDU log event cost and DDU custom event cost pages.