oci-monitoring

OCI NodeJS client for Monitoring Service

This module enables you to write code to manage resources for Monitoring Service.

Requirements

To use this module, you must have the following:

• An Oracle Cloud Infrastructure account.
• A user created in that account, in a group with a policy that grants the desired permissions. This can be a user for yourself, or another person/system that needs to call the API. For an example of how to set up a new user, group, compartment, and policy, see Adding Users. For a list of typical policies you may want to use, see Common Policies.
• A key pair used for signing API requests, with the public key uploaded to Oracle. Only the user calling the API should be in possession of the private key. For more information, see Configuring Credentials

Installing

Use the following command to install this module:

npm install oci-monitoring

Alternatively you can git clone this repo.

Changelog

2.55.0 - 2023-03-21

Added

• Support for backup automation integration with the Database Recovery service in the Database service
• Support for changing the disaster recovery configuration of an autonomous database in remote regions of its disaster recovery association in the Database service
• Support for creating a remote disaster recovery association clone of an autonomous database in the Database service
• Support for managed build stages to be configured to use custom shape build runners in the DevOps service
• Support for listing pre-built functions and creating functions from pre-built functions in the Functions service
• Support for connections types for database resources of type Amazon S3, HDFS, SQL Server, Java Messaging service, Mongo DB, Oracle NoSQL, and Snowflake in the GoldenGate service

Breaking Changes

• The field lifecycleState is changed from type FunctionSummary.LifecycleState to string in the FunctionSummary model in the Functions service
• The enum value LAKE_HOUSE_CONNECTION was renamed to LAKE_CONNECTION in the Connection, ConnectionDetails, ConnectionSummary, CreateConnectionDetails and UpdateConnectionDetails models in the Data Integration Service
• The enum value LAKE_HOUSE_DATA_ASSET was renamed to LAKE_DATA_ASSET in the DataAsset, CreateDataAssetDetails, DataAssetSummary, and UpdateDataAssetDetails models in the Data Integration Service
• The models ConnectionFromLakehouse, ConnectionFromLakehouseDetails, ConnectionSummaryFromLakehouse, CreateConnectionFromLakehouse, CreateDataAssetFromLakehouse, DataAssetFromLakehouseDetails, DataAssetSummaryFromLakehouse, UpdateConnectionFromLakehouse, UpdateDataAssetFromLakehouse have been removed from the Data Integration service