Two components that the Management Agent solution includes in the Cloud service are:

Management Agent. Management Agent is a lightweight process that collects and sends operational data from your resources to OCI services, such as Monitoring, Logging, or Stack Monitoring. Management Agent can collect data from various sources, such as databases, hosts, or applications.

Management Gateway. Management Gateway is a component that enables secure communication between Management Agents and OCI services. Management Gateway acts as a proxy that encrypts and forwards data from Management Agents to OCI services.

To grant the CloudOps group the ability to view and retrieve monitoring metrics only for all monitoring-enabled compute instances, you need to use a policy statement with a condition that filters by the metric namespace. The metric namespace is a unique name that identifies the source of the metrics. For compute instances, the metric namespace is oci_computeagent. Therefore, the policy statement should be: Allow group cloudops to read metrics in tenancy where target.metrics.namespace='oci_computeagent'

Two items that describe the capabilities of the OCI Database Management Service are:

Perform management tasks across a group of databases. Database Management Service provides a feature called Database Fleet Management that allows you to perform management tasks across a group of databases in your tenancy. You can use Database Fleet Management to view and compare the configuration, performance, and security of your databases. You can also use Database Fleet Management to execute SQL commands or scripts on multiple databases at once.

Monitor database performance. Database Management Service also provides various tools and dashboards that let you monitor the performance of your databases and SQL statements. You can use Performance Hub to view real-time and historical performance data of your databases. You can also use SQL Monitor to view real-time and historical execution details of your SQL statements.

Two features of OCI that can help you archive Info-level logging data of these instances into the OCI Object Storage are:

Service Connectors. Service Connectors are components of Service Connector Hub that enable data movement between OCI services. You can create a service connector that has Logging as the source service and Object Storage as the target service. You can also specify filters to select only the Info-level logs from your instances.

ObjectCollection Rule. ObjectCollection Rule is a feature of Logging Analytics that allows you to collect log data from objects stored in Object Storage buckets. You can create an ObjectCollection Rule that specifies the bucket name, object name pattern, entity type, and log source for your log data. For more information, see [Service Connector Hub Overview] and [ObjectCollection Rule].

Application Performance Monitoring tracks all related spans for a single user request using Trace ID. A trace is a collection of spans that represent a single user request or transaction. A span is a unit of work within a trace, such as an HTTP request or a database query. Each trace has a unique Trace ID that identifies it across different services and components. You can use Trace ID to search and analyze traces in Application Performance Monitoring. For more information, seeTraces and Spans.