In OCI Stack Monitoring, once Management Agents are deployed and resources (e.g., databases,

applications) are discovered, the immediate next step is the collection of metric data.

Metric data is immediately collected (A): Management Agents are lightweight processes that

continuously collect performance and health metrics from discovered resources (e.g., CPU usage,

memory utilization) and send them to OCI services like Monitoring or Stack Monitoring. This data

becomes available for visualization and analysis right after discovery.

Why not B, C, or D?

Alarm rules (B): Alarms are configured separately in the OCI Monitoring service and only trigger after

metric data is collected and thresholds are breached—not an immediate post-discovery action.

Resource discovery (C): Discovery happens before this stage, as the question assumes resources are

already discovered. Agents don’t rediscover resources post-setup.

Notifications (D): Notifications require separate configuration (e.g., via the Notifications service) and

are not an automatic outcome of agent setup and discovery.

This aligns with Stack Monitoring’s purpose of providing real-time visibility into resource

performance.

Reference: Stack Monitoring Overview, Management Agent