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:
Refer to Oracle documentation for details on how to set up the monitoring endpoint access:
Import Tags
To import tags from OCI, two additional configuration options are required:
Refer to the documentation for creating an API token with the correct scopes.