The image shows the architecture for monitoring and tracing microservices with Oracle Cloud Infrastructure Application Performance Monitoring Cloud Service (APM).

The architecture includes a single Oracle Cloud Infrastructure (OCI) region that provides APM and APM Domain services. Users access microservices from the internet. The APM browser agent captures the user actions done on the browser.

The region includes 2 virtual cloud networks (VCNs). The primary VCN includes 2 subnets: a public subnet that includes a shared file system and a private subnet that includes an Oracle Container Engine for Kubernetes (OKE) cluster. The OKE cluster includes 2 microservices replicas, the APM Java Agent, and a persistent volume that connects to the shared file system. A secondary VCN includes a private subnet that provides Oracle Autonomous Transaction Processing as an example microservices deployment.

Data flow in this architecture is depicted by letter-labeled arrows between components:

• (A) APM Java Agent deployed to Kubernetes pods
  1. Create an APM domain in OCI and obtain the data upload endpoint URL and private and public data keys of the domain.
  2. Create a shared file system in OCI, and then create Kubernetes storage objects such as persistent volume in the OKE cluster.
  3. Download the APM Java agent from the APM domain, and provision it in the mounted volume.
  4. Deploy the APM agent to the application by updating the YAML files for the Kubernetes Deployments or StatefulSets.
• (B) Server and JDBC traces, spans, and metrics sent to APM domain

  After the Kubernetes pods are restarted, traces and spans from the server are sent to the APM domain where the data-upload endpoint URL is.

• (C) Browser traces, spans, and metrics sent to APM domain

  Collected data can be visualized in the APM dashboards and Trace Explorer for performance and availability analysis.