{"id":955,"date":"2026-04-17T06:35:33","date_gmt":"2026-04-17T06:35:33","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-fleet-application-management-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-observability-and-management\/"},"modified":"2026-04-17T06:35:33","modified_gmt":"2026-04-17T06:35:33","slug":"oracle-cloud-fleet-application-management-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-observability-and-management","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-fleet-application-management-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-observability-and-management\/","title":{"rendered":"Oracle Cloud Fleet Application Management Tutorial: Architecture, Pricing, Use Cases, and Hands-On Guide for Observability and Management"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Category<\/h2>\n\n\n\n<p>Observability and Management<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Introduction<\/h2>\n\n\n\n<p>Fleet Application Management is an <strong>Oracle Cloud (OCI)<\/strong> service in the <strong>Observability and Management<\/strong> category that helps you <strong>discover, organize, and manage applications as a fleet<\/strong>\u2014instead of treating every host as a one-off snowflake.<\/p>\n\n\n\n<p>In simple terms: <strong>you connect your servers, let OCI identify supported application installations and deployments, group them into a \u201cfleet,\u201d and then use one place to view inventory and perform management tasks<\/strong> (depending on what application types and actions are supported in your tenancy\/region).<\/p>\n\n\n\n<p>Technically, Fleet Application Management relies on OCI\u2019s management instrumentation (commonly the <strong>OCI Management Agent<\/strong>, depending on your environment and the application types you manage) to collect application signals and inventory. It then models this information as OCI resources (fleets, managed entities, application instances\/deployments) and applies standard OCI governance: <strong>compartments, IAM policies, tags, audit logs<\/strong>, and (where applicable) integrations with <strong>Logging\/Monitoring\/Notifications<\/strong>.<\/p>\n\n\n\n<p>The problem it solves is operational sprawl: as the number of environments, hosts, and application instances grows, teams struggle with:\n&#8211; consistent application inventory,\n&#8211; visibility of \u201cwhat\u2019s running where,\u201d\n&#8211; safe, repeatable operations across many instances,\n&#8211; governance and access control at scale.<\/p>\n\n\n\n<blockquote>\n<p>Service status note: At the time of writing, Oracle\u2019s product documentation lists the service as <strong>Fleet Application Management<\/strong>. If you encounter older blog posts or internal references using abbreviations (for example, \u201cFAM\u201d), confirm terminology and current capabilities in the official documentation for your region\/tenancy.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is Fleet Application Management?<\/h2>\n\n\n\n<p><strong>Official purpose (high level)<\/strong><br\/>\nFleet Application Management is designed to provide a centralized way to <strong>manage applications across a fleet of hosts\/environments<\/strong> in Oracle Cloud. The service focuses on <strong>fleet-level<\/strong> visibility and operations rather than host-by-host manual work.<\/p>\n\n\n\n<p><strong>Core capabilities (conceptual)<\/strong><br\/>\nWhile exact capabilities can vary by supported application type and region, the typical scope of Fleet Application Management includes:\n&#8211; <strong>Application discovery \/ inventory<\/strong> for supported application types installed on connected hosts\n&#8211; <strong>Fleet grouping<\/strong> to represent sets of applications that should be managed together (by environment, business unit, lifecycle stage, compliance boundary, etc.)\n&#8211; <strong>Centralized views<\/strong> of application deployments\/instances and their metadata\n&#8211; <strong>Governed operations<\/strong> using OCI compartments, IAM, tags, and audit logs<\/p>\n\n\n\n<p><strong>Major components (how to think about it in OCI terms)<\/strong>\n&#8211; <strong>Fleet<\/strong>: The primary resource you create to group and manage applications at scale.\n&#8211; <strong>Managed hosts \/ managed entities<\/strong>: Compute instances or external hosts that are connected to OCI for discovery\/management.\n&#8211; <strong>Discovery\/collection mechanism<\/strong>: Typically the <strong>OCI Management Agent<\/strong> (exact mechanism depends on the workload; verify in official docs for your app type).\n&#8211; <strong>OCI governance controls<\/strong>: Compartments, IAM policies, tags, audit logs, and (optionally) events\/notifications.<\/p>\n\n\n\n<p><strong>Service type<\/strong><br\/>\nA <strong>managed OCI control-plane service<\/strong> for application fleet operations (inventory and management workflows), integrated with standard OCI identity and governance.<\/p>\n\n\n\n<p><strong>Scope (regional\/global\/account-scoped)<\/strong><br\/>\nFleet Application Management is an OCI service that you use within a <strong>tenancy<\/strong> and typically within a <strong>region<\/strong>, with resources organized by <strong>compartments<\/strong>.<br\/>\nBecause OCI services differ in how they store and present data regionally, <strong>verify the regional behavior and cross-region visibility in the official docs<\/strong> for your tenancy and the specific features you plan to use.<\/p>\n\n\n\n<p><strong>How it fits into the Oracle Cloud ecosystem<\/strong>\nFleet Application Management is part of the broader <strong>Observability and Management<\/strong> toolset and commonly complements:\n&#8211; <strong>Monitoring<\/strong> and <strong>Alarms<\/strong> (service health metrics and alerting)\n&#8211; <strong>Logging<\/strong> (operational logs for troubleshooting)\n&#8211; <strong>Notifications<\/strong> (routing alerts\/events)\n&#8211; <strong>Events<\/strong> (automation triggers)\n&#8211; <strong>OS Management Hub \/ patching services<\/strong> (host-level patching\/compliance)\n&#8211; <strong>Resource Manager (Terraform)<\/strong> (infrastructure provisioning)\n&#8211; <strong>Vault<\/strong> (secrets and key management)<\/p>\n\n\n\n<p>Official documentation entry point (start here):<br\/>\n&#8211; Fleet Application Management docs: https:\/\/docs.oracle.com\/en-us\/iaas\/fleet-application-management\/home.htm (verify URL if it redirects in your region)<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use Fleet Application Management?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Business reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Reduce operational cost<\/strong> by managing groups of application instances with consistent processes.<\/li>\n<li><strong>Increase auditability<\/strong>: centralized inventory and controlled operations make it easier to answer \u201cwhat\u2019s deployed where\u201d for audits and risk reviews.<\/li>\n<li><strong>Support environment growth<\/strong>: as teams scale to dozens\/hundreds of servers, manual tracking breaks down.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Technical reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Inventory and discovery<\/strong>: identify application installations\/deployments across many hosts in a consistent way (for supported app types).<\/li>\n<li><strong>Standardize fleet constructs<\/strong>: represent your architecture in a manageable model (fleets by environment or product line).<\/li>\n<li><strong>Integrate with OCI governance<\/strong>: use compartments and IAM rather than building your own RBAC database.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Faster troubleshooting<\/strong>: faster identification of impacted application instances and where they run.<\/li>\n<li><strong>Repeatable workflows<\/strong>: less \u201ctribal knowledge\u201d required to manage widely distributed application estates.<\/li>\n<li><strong>Better change planning<\/strong>: centralized view helps plan updates and coordinate changes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/compliance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Least privilege access<\/strong> via IAM policies.<\/li>\n<li><strong>Improved accountability<\/strong> via OCI audit logs (who created fleets, changed configurations, initiated actions).<\/li>\n<li><strong>Stronger separation of duties<\/strong> using compartments and policies aligned to org structure.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scalability\/performance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Fleet-first model<\/strong> scales better than per-host manual operations.<\/li>\n<li><strong>Central control plane<\/strong> reduces the need for custom tooling to aggregate inventory and metadata.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose it<\/h3>\n\n\n\n<p>Choose Fleet Application Management when:\n&#8211; you have <strong>many application instances<\/strong> (or expect to),\n&#8211; you need a <strong>central inventory<\/strong> across environments,\n&#8211; you want <strong>OCI-governed operations<\/strong> on applications (not just hosts),\n&#8211; your app stack matches the <strong>supported discovery\/management scope<\/strong> for the service (verify in docs).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose it<\/h3>\n\n\n\n<p>It may not be a fit when:\n&#8211; you only have a handful of hosts and can manage manually,\n&#8211; you primarily need <strong>deep application performance tracing<\/strong> (consider OCI APM instead),\n&#8211; your applications are fully managed PaaS\/SaaS with no host-level footprint to discover,\n&#8211; you need management for an application type not supported by Fleet Application Management (verify supported types in docs).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is Fleet Application Management used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Financial services (regulated environments needing inventory\/auditability)<\/li>\n<li>Healthcare (compliance and environment segmentation)<\/li>\n<li>Retail\/e-commerce (multiple environments, rapid change)<\/li>\n<li>Manufacturing (mixed on-prem + cloud footprints)<\/li>\n<li>Government\/public sector (strict governance, compartmentalization)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Team types<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Platform engineering teams building internal platforms on OCI<\/li>\n<li>DevOps\/SRE teams responsible for uptime and change management<\/li>\n<li>Operations teams migrating from legacy CMDB\/manual inventory<\/li>\n<li>Security engineering teams supporting compliance reporting<\/li>\n<li>Application operations teams managing packaged middleware stacks<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Traditional VM-based applications<\/li>\n<li>Hybrid estates (OCI + on-prem) where supported by the agent and connectivity model<\/li>\n<li>Enterprise application stacks where version visibility and change control matter<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Architectures<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Multi-compartment enterprise landing zones<\/li>\n<li>Hub-and-spoke networking with centralized governance<\/li>\n<li>Blue\/green and multi-environment (dev\/test\/stage\/prod) footprints<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Real-world deployment contexts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Central IT managing fleets for multiple business units<\/li>\n<li>Product teams that own an application but share base infrastructure<\/li>\n<li>MSPs managing multiple customer compartments\/tenancies (where allowed)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Production vs dev\/test usage<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Production<\/strong>: most valuable for inventory, governance, and repeatable operational workflows.<\/li>\n<li><strong>Dev\/test<\/strong>: useful to standardize how app deployments are cataloged and managed; also helps validate discovery and access models before production rollout.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">5. Top Use Cases and Scenarios<\/h2>\n\n\n\n<p>Below are realistic scenarios where Fleet Application Management is commonly useful. Exact capabilities depend on supported application types and your setup\u2014verify the service\u2019s supported discovery and actions in official docs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Fleet-wide application inventory for audits<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Audit asks for a list of application instances, versions, and where they run.<\/li>\n<li><strong>Why this fits<\/strong>: Fleet model centralizes inventory across many hosts.<\/li>\n<li><strong>Example<\/strong>: Security team needs quarterly evidence that only approved application versions are running in the Prod compartment.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Environment segmentation (dev\/test\/prod) with separate access<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Too many people have production visibility or control.<\/li>\n<li><strong>Why this fits<\/strong>: OCI compartments + fleet resources let you segment visibility\/management.<\/li>\n<li><strong>Example<\/strong>: Create <code>Payments-Prod-Fleet<\/code> in the Prod compartment; grant only SREs manage access.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Operational readiness during migrations to OCI<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: During lift-and-shift, teams lose track of what moved and what\u2019s still on-prem.<\/li>\n<li><strong>Why this fits<\/strong>: Discovery and centralized inventory help track migration progress.<\/li>\n<li><strong>Example<\/strong>: A migration factory uses Fleet Application Management to confirm all expected app instances appear in OCI.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Post-incident blast radius analysis<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A host failure occurs; teams need to know which application instances were affected.<\/li>\n<li><strong>Why this fits<\/strong>: Fleet\/grouping and inventory views reduce time-to-identify.<\/li>\n<li><strong>Example<\/strong>: A compute node reboot causes outage; operations check the fleet to identify impacted deployments.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Standardized tagging and ownership tracking<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: No consistent \u201cowner\u201d metadata for applications across environments.<\/li>\n<li><strong>Why this fits<\/strong>: OCI tags (defined\/freeform) applied to fleets can enforce ownership.<\/li>\n<li><strong>Example<\/strong>: Enforce tags like <code>CostCenter<\/code>, <code>AppOwner<\/code>, <code>DataClassification<\/code> on fleets.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Operational handoffs between teams<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Dev teams deploy, ops teams run\u2014but asset inventory is incomplete.<\/li>\n<li><strong>Why this fits<\/strong>: Fleet provides a shared operational object and consistent visibility.<\/li>\n<li><strong>Example<\/strong>: New service onboarding requires adding deployments to a fleet before production go-live.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Multi-region operational visibility (where supported)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Teams run active-active stacks in multiple regions and need consistent inventory.<\/li>\n<li><strong>Why this fits<\/strong>: Fleet constructs and compartments can align operational ownership; verify multi-region behavior in docs.<\/li>\n<li><strong>Example<\/strong>: Regional SREs manage their own fleets; central team reviews standardized reports.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Compliance boundary enforcement by compartment and fleet<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A regulated application must be strictly isolated and monitored.<\/li>\n<li><strong>Why this fits<\/strong>: Use dedicated compartment + fleet + IAM policies.<\/li>\n<li><strong>Example<\/strong>: HIPAA workload uses a dedicated compartment and fleet with restricted operators.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Change planning across many app instances<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A planned change affects many instances; you need to identify scope.<\/li>\n<li><strong>Why this fits<\/strong>: Fleet-level inventory supports safer planning.<\/li>\n<li><strong>Example<\/strong>: A library update requires identifying which instances depend on a specific runtime.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Building a lightweight CMDB substitute for app estates<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: CMDB data is stale; manual spreadsheets are inaccurate.<\/li>\n<li><strong>Why this fits<\/strong>: Automated discovery and centralized inventory reduce drift.<\/li>\n<li><strong>Example<\/strong>: Replace \u201capp server spreadsheet\u201d with fleet inventory views and tag-driven reporting.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<p>Because Oracle Cloud services evolve, treat this section as a practical guide and <strong>confirm exact feature availability (supported application types, actions, and regions) in the official Fleet Application Management documentation<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Fleet resource model (fleet-based organization)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Lets you define a \u201cfleet\u201d as a logical grouping for application management.<\/li>\n<li><strong>Why it matters<\/strong>: You manage by <em>group<\/em>, not by host.<\/li>\n<li><strong>Practical benefit<\/strong>: Cleaner operations for multi-environment deployments; faster scoping for incidents and changes.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Fleet design is only as good as your compartment\/tagging strategy.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Application discovery and inventory (for supported app types)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Collects metadata about application installations\/deployments from managed hosts.<\/li>\n<li><strong>Why it matters<\/strong>: You can\u2019t manage what you can\u2019t reliably inventory.<\/li>\n<li><strong>Practical benefit<\/strong>: Central view of \u201cwhat is running where\u201d without manual tracking.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Discovery depends on supported application types and correct agent connectivity\/permissions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Managed host onboarding (agent-based connectivity)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Connects OCI compute instances (and potentially external hosts, depending on supported modes) to OCI so they can be inventoried\/managed.<\/li>\n<li><strong>Why it matters<\/strong>: Fleet Application Management needs a trusted way to communicate with hosts.<\/li>\n<li><strong>Practical benefit<\/strong>: Standard onboarding and credentialing; reduced bespoke scripts.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Requires network egress to OCI endpoints and correct OS prerequisites.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compartment and IAM integration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Uses OCI IAM policies to control who can view\/manage fleets and related resources.<\/li>\n<li><strong>Why it matters<\/strong>: Governance is essential for production operations.<\/li>\n<li><strong>Practical benefit<\/strong>: Least privilege; separation of duties; consistent enterprise controls.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Mis-scoped policies can lead to over-permissioning or blocked operations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tagging support (cost\/governance metadata)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Supports applying OCI tags to fleets\/resources (where available).<\/li>\n<li><strong>Why it matters<\/strong>: Tagging drives cost allocation, ownership, and automation.<\/li>\n<li><strong>Practical benefit<\/strong>: Better reporting; easier ops automation via tag-based queries.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Tag compliance requires organizational discipline; consider tag defaults and tag namespaces.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Auditability (OCI Audit)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Records control-plane actions in OCI Audit.<\/li>\n<li><strong>Why it matters<\/strong>: You need a forensics trail of who changed what.<\/li>\n<li><strong>Practical benefit<\/strong>: Incident response, compliance evidence, and change accountability.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Audit logs show control-plane operations; they don\u2019t replace workload-level logging.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Integration patterns with monitoring and notifications (where applicable)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Enables operational workflows where fleet changes or detected events can be integrated into Monitoring\/Events\/Notifications.<\/li>\n<li><strong>Why it matters<\/strong>: Operations teams rely on alerting and ticket automation.<\/li>\n<li><strong>Practical benefit<\/strong>: Consistent \u201cdetect \u2192 notify \u2192 remediate\u201d loops.<\/li>\n<li><strong>Limitations\/caveats<\/strong>: Exact event types and metrics vary\u2014verify in docs for your region.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">7. Architecture and How It Works<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">High-level architecture<\/h3>\n\n\n\n<p>Fleet Application Management uses a <strong>control plane<\/strong> in OCI that stores fleet definitions and inventory metadata. Managed hosts run an <strong>agent\/collector<\/strong> that:\n1. securely registers with OCI,\n2. collects application metadata from the host (for supported app types),\n3. sends inventory\/telemetry to the service endpoints.<\/p>\n\n\n\n<p>OCI then provides:\n&#8211; UI and APIs to view and manage fleets\n&#8211; governance via compartments\/IAM\n&#8211; audit logging of actions<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Request\/data\/control flow (conceptual)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Operator<\/strong> creates a Fleet in an OCI compartment.<\/li>\n<li><strong>Operator<\/strong> onboards hosts by installing and registering an agent.<\/li>\n<li>The agent performs discovery\/collection and sends metadata to OCI.<\/li>\n<li>Fleet Application Management correlates hosts and application entities into the fleet model.<\/li>\n<li>Operators query inventory, review status, and perform supported management actions.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related OCI services (common patterns)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>IAM<\/strong>: fine-grained access control to fleet resources.<\/li>\n<li><strong>Audit<\/strong>: records control-plane changes and operations.<\/li>\n<li><strong>Monitoring\/Alarms<\/strong>: alert on operational signals (verify which metrics are available for Fleet Application Management).<\/li>\n<li><strong>Logging<\/strong>: capture agent logs and service logs if configured (often via separate logging configuration).<\/li>\n<li><strong>Events + Notifications<\/strong>: automation hooks (verify event types for Fleet Application Management).<\/li>\n<li><strong>Vault<\/strong>: store secrets needed for operational tooling around fleets (not necessarily required by the service itself).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OCI Identity and Access Management (IAM)<\/strong><\/li>\n<li><strong>Networking<\/strong> (VCN\/subnet for compute instances; outbound egress to OCI endpoints)<\/li>\n<li><strong>Compute<\/strong> (if you manage app instances on VMs)<\/li>\n<li><strong>Management Agent<\/strong> (commonly used for host connectivity\u2014verify exact agent requirements in docs)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/authentication model (conceptual)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Users authenticate via <strong>OCI IAM<\/strong>.<\/li>\n<li>Agents authenticate using OCI-managed mechanisms established during agent registration (commonly via install keys\/certificates; verify specifics in docs).<\/li>\n<li>Authorization is enforced by IAM policies at the compartment\/tenancy level.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Networking model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Managed hosts typically require <strong>outbound connectivity<\/strong> to OCI service endpoints.<\/li>\n<li>If hosts are in private subnets, you commonly need a <strong>NAT Gateway<\/strong> or <strong>Service Gateway<\/strong> (depending on endpoint support) so the agent can reach OCI.<\/li>\n<li>In locked-down environments, allowlisting OCI endpoints and controlling egress is critical.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monitoring\/logging\/governance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Treat fleets as first-class operational assets: enforce tags, naming standards, and access boundaries.<\/li>\n<li>Capture agent logs centrally (for example, via OCI Logging) to speed up troubleshooting.<\/li>\n<li>Use compartments to map to environments and compliance boundaries.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Simple architecture diagram (conceptual)<\/h4>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  U[Operator \/ SRE] --&gt;|Console \/ API| FAM[Fleet Application Management&lt;br\/&gt;Control Plane]\n  subgraph VCN[OCI VCN]\n    H1[Compute Instance(s)&lt;br\/&gt;App + Agent]\n  end\n  H1 --&gt;|Inventory\/Discovery Data| FAM\n  FAM --&gt; IAM[IAM Policies \/ Compartments]\n  FAM --&gt; AUD[Audit Logs]\n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Production-style architecture diagram (multi-environment)<\/h4>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph Tenancy[OCI Tenancy]\n    IAM[IAM&lt;br\/&gt;Groups, Policies, Dynamic Groups]\n    AUD[Audit]\n    NOTIF[Notifications]\n    EVT[Events]\n    LOG[Logging]\n    MON[Monitoring &amp; Alarms]\n\n    subgraph ProdComp[Compartment: Prod]\n      FAMProd[Fleet Application Management&lt;br\/&gt;Prod Fleet(s)]\n      subgraph ProdVCN[Prod VCN]\n        NAT1[NAT Gateway]\n        P1[App Hosts (Private Subnet)&lt;br\/&gt;Agent installed]\n      end\n    end\n\n    subgraph DevComp[Compartment: Dev\/Test]\n      FAMDev[Fleet Application Management&lt;br\/&gt;Dev Fleet(s)]\n      subgraph DevVCN[Dev VCN]\n        NAT2[NAT Gateway]\n        D1[App Hosts (Private Subnet)&lt;br\/&gt;Agent installed]\n      end\n    end\n  end\n\n  P1 --&gt;|Egress via NAT| FAMProd\n  D1 --&gt;|Egress via NAT| FAMDev\n\n  FAMProd --&gt; AUD\n  FAMDev --&gt; AUD\n  FAMProd --&gt; EVT --&gt; NOTIF\n  FAMDev --&gt; EVT --&gt; NOTIF\n  LOG --- P1\n  MON --- FAMProd\n  MON --- FAMDev\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">8. Prerequisites<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Tenancy\/account requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An active <strong>Oracle Cloud<\/strong> tenancy.<\/li>\n<li>Access to an OCI <strong>compartment<\/strong> where you can create\/manage:<\/li>\n<li>Fleet Application Management resources<\/li>\n<li>any required agent resources\/keys (depending on onboarding method)<\/li>\n<li>compute\/network resources for the lab<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM roles<\/h3>\n\n\n\n<p>For a beginner lab, the simplest approach is:\n&#8211; Use a user\/group with broad permissions in a dedicated lab compartment (for example, permissions equivalent to \u201cmanage all-resources\u201d in that compartment).<\/p>\n\n\n\n<p>For production, create least-privilege policies for:\n&#8211; fleet creation and management\n&#8211; host onboarding\/agent management\n&#8211; read-only access for auditors<\/p>\n\n\n\n<blockquote>\n<p>IAM policy syntax and service \u201cresource family\u201d names can change or be service-specific. Use the official IAM policy reference in the Fleet Application Management and Management Agent documentation and <strong>verify exact policy statements<\/strong>.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Billing requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Your tenancy must have billing enabled for paid resources used in the lab (primarily <strong>Compute<\/strong>, <strong>Block Volume<\/strong>, <strong>NAT Gateway<\/strong>, and data egress where applicable).<\/li>\n<li>Fleet Application Management pricing may be separate or may have $0 control-plane cost depending on Oracle\u2019s pricing model\u2014<strong>verify on the official pricing page<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tools needed<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI Console access<\/li>\n<li>SSH client (<code>ssh<\/code>) to connect to a compute instance<\/li>\n<li>A terminal on your workstation<\/li>\n<li>(Optional) OCI CLI if you prefer automation. Not required for this lab.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Region availability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Fleet Application Management availability can be region-dependent. Confirm in:<\/li>\n<li>OCI Console service list for your region<\/li>\n<li>Official docs region notes (if provided)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas\/limits<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Compute instance limits (per shape, cores, VNICs)<\/li>\n<li>VCN\/NAT Gateway limits<\/li>\n<li>Any Fleet Application Management service limits (verify in official docs)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OCI Compute<\/strong>: to host a sample application<\/li>\n<li><strong>OCI Networking<\/strong>: VCN, subnet, and egress path<\/li>\n<li><strong>OCI Management Agent<\/strong> (commonly): to connect the host for discovery\/management<\/li>\n<\/ul>\n\n\n\n<p>Management Agent docs entry point (verify URL if it redirects):<br\/>\n&#8211; https:\/\/docs.oracle.com\/en-us\/iaas\/management-agent\/home.htm<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing model (what to check)<\/h3>\n\n\n\n<p>Oracle Cloud pricing for Observability and Management services can vary by:\n&#8211; region\n&#8211; service feature\/SKU\n&#8211; data volume (GB ingested\/stored), if applicable\n&#8211; number of managed entities\/agents, depending on service<\/p>\n\n\n\n<p>For Fleet Application Management specifically, <strong>do not assume it is free or paid<\/strong> without checking current pricing. Use:\n&#8211; OCI\/Oracle Cloud price list: https:\/\/www.oracle.com\/cloud\/price-list\/\n&#8211; OCI Cost Estimator: https:\/\/www.oracle.com\/cloud\/costestimator.html<\/p>\n\n\n\n<p>Navigate the price list to <strong>Observability and Management<\/strong> and locate <strong>Fleet Application Management<\/strong> (if listed) or any dependency SKUs that apply.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Common pricing dimensions (practical cost drivers)<\/h3>\n\n\n\n<p>Even if Fleet Application Management control plane is low-cost or $0, you still pay for dependencies:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Compute instances<\/strong>\n   &#8211; OCPU and memory pricing for the hosts you manage\n   &#8211; Boot volumes and block volumes<\/li>\n<li><strong>Network egress<\/strong>\n   &#8211; Outbound data transfer from OCI to the internet or between regions\n   &#8211; NAT Gateway processing (and data processing) where applicable<\/li>\n<li><strong>Logging\/Monitoring storage<\/strong>\n   &#8211; If you forward agent logs or store additional logs\/metrics, you may incur ingestion and storage costs (depending on which logging\/analytics services you enable).<\/li>\n<li><strong>Operations overhead<\/strong>\n   &#8211; Extra compute overhead on hosts (agent CPU\/memory)\n   &#8211; Operational time to maintain least privilege and fleet governance<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Free tier considerations<\/h3>\n\n\n\n<p>Oracle Cloud has an Always Free tier for some services, but <strong>eligibility and included limits vary<\/strong>. Verify Always Free coverage for:\n&#8211; compute shapes (if using Always Free eligible VM shapes)\n&#8211; monitoring\/logging usage\n&#8211; any Fleet Application Management-specific free quota (if offered)<\/p>\n\n\n\n<p>Always Free overview (verify current limits):<br\/>\n&#8211; https:\/\/www.oracle.com\/cloud\/free\/<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Hidden\/indirect costs to watch<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>NAT Gateway<\/strong>: In private subnet designs, NAT Gateway can become a steady monthly cost driver.<\/li>\n<li><strong>Cross-region data movement<\/strong>: If you centralize logging or inventory across regions, data transfer can add up.<\/li>\n<li><strong>Log retention<\/strong>: Long retention periods cost money\u2014set retention based on compliance needs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How to optimize cost<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Start with <strong>one small fleet<\/strong> and a minimal number of hosts.<\/li>\n<li>Prefer <strong>private subnets<\/strong> with controlled egress; design egress intentionally.<\/li>\n<li>Don\u2019t enable expensive analytics features \u201cjust in case.\u201d<\/li>\n<li>Set log retention to the minimum that meets compliance.<\/li>\n<li>Use tags for cost tracking: <code>CostCenter<\/code>, <code>Environment<\/code>, <code>App<\/code>, <code>Owner<\/code>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example low-cost starter estimate (qualitative)<\/h3>\n\n\n\n<p>A low-cost lab typically includes:\n&#8211; 1 small compute VM\n&#8211; 1 VCN + 1 subnet\n&#8211; (optional) NAT Gateway if you place the VM in a private subnet\n&#8211; minimal log retention<\/p>\n\n\n\n<p>Exact numbers are region- and SKU-dependent, so use the OCI Cost Estimator to model:\n&#8211; VM shape cost\n&#8211; NAT Gateway + data processing\n&#8211; expected data egress and logging<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations<\/h3>\n\n\n\n<p>In production, cost typically scales with:\n&#8211; number of hosts\n&#8211; number of environments\/regions\n&#8211; amount of operational telemetry you ingest\/store\n&#8211; security posture (private endpoints, centralized logging, extended retention)<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<p>This lab focuses on a <strong>safe, minimal<\/strong> setup: one OCI compute instance, a management agent installed on it, and a Fleet Application Management fleet that can \u201csee\u201d the host and run discovery (where supported).<\/p>\n\n\n\n<p>Because application discovery depends on supported application types, your \u201cdiscovered applications\u201d results may vary. The lab is still valid if you end with:\n&#8211; a registered managed host\/agent visible in OCI, and\n&#8211; a fleet created and associated with that host.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Create a Fleet in <strong>Fleet Application Management<\/strong><\/li>\n<li>Provision a small OCI compute instance<\/li>\n<li>Install and register the required agent (commonly OCI Management Agent)<\/li>\n<li>Confirm the host appears in Fleet Application Management and that discovery\/inventory runs (as supported)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n1. Create a compartment and basic network (or reuse existing).\n2. Create a compute instance.\n3. Ensure outbound connectivity from the instance to OCI endpoints.\n4. Install and register the Management Agent (using the console-generated install workflow).\n5. Create a Fleet and associate the managed host.\n6. Validate visibility and inventory.\n7. Clean up resources to avoid ongoing costs.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Prepare a compartment (recommended)<\/h3>\n\n\n\n<p><strong>Console path<\/strong>: Identity &amp; Security \u2192 Compartments<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Create a compartment like:\n   &#8211; Name: <code>lab-fam<\/code>\n   &#8211; Description: <code>Fleet Application Management lab<\/code><\/li>\n<li>Record the compartment OCID (optional).<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You have an isolated place to create and delete resources safely.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; In the compartment list, you can select <code>lab-fam<\/code> and it shows as Active.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Create networking (VCN + subnet)<\/h3>\n\n\n\n<p>If you already have a VCN\/subnet you can use, reuse it. Otherwise:<\/p>\n\n\n\n<p><strong>Console path<\/strong>: Networking \u2192 Virtual Cloud Networks \u2192 Start VCN Wizard<\/p>\n\n\n\n<p>Choose either:\n&#8211; <strong>Public subnet<\/strong> (simpler for labs; fewer moving parts), or\n&#8211; <strong>Private subnet + NAT Gateway<\/strong> (closer to production patterns).<\/p>\n\n\n\n<p><strong>Recommended lab-simple option<\/strong>: Public subnet<br\/>\n&#8211; Create VCN with Internet Gateway and a public subnet.\n&#8211; Ensure the subnet has a route rule to the Internet Gateway.\n&#8211; Ensure the instance will get a public IP.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Instance will have outbound internet access (needed to reach OCI endpoints for agent registration and updates).<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Subnet route table includes a default route (<code>0.0.0.0\/0<\/code>) to the Internet Gateway.\n&#8211; Security list allows outbound traffic (default is usually permissive egress).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Create a small compute instance<\/h3>\n\n\n\n<p><strong>Console path<\/strong>: Compute \u2192 Instances \u2192 Create instance<\/p>\n\n\n\n<p>Suggested lab settings:\n&#8211; Name: <code>fam-lab-vm1<\/code>\n&#8211; Image: Oracle Linux (choose a current supported Oracle Linux image)\n&#8211; Shape: a small VM shape suitable for labs\n&#8211; Network: select your lab VCN and subnet\n&#8211; SSH keys: add your public key\n&#8211; Public IP: enabled (if using public subnet)<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Instance is running and you can SSH into it.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Instance lifecycle state is <code>RUNNING<\/code>.\n&#8211; Note the public IP address (or private IP if you use bastion).<\/p>\n\n\n\n<p>SSH to the instance:<\/p>\n\n\n\n<pre><code class=\"language-bash\">ssh -i ~\/.ssh\/id_rsa opc@&lt;PUBLIC_IP&gt;\n<\/code><\/pre>\n\n\n\n<p>If you used Oracle Linux and the default user differs, follow the \u201cInstance access\u201d details shown in the OCI console for the image you selected.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Install a simple sample workload (optional but useful)<\/h3>\n\n\n\n<p>This step isn\u2019t strictly required for fleet onboarding, but it helps ensure the host looks realistic.<\/p>\n\n\n\n<p>On the instance:<\/p>\n\n\n\n<pre><code class=\"language-bash\">sudo dnf -y update || sudo yum -y update\n<\/code><\/pre>\n\n\n\n<p>Install a lightweight web server (example):<\/p>\n\n\n\n<pre><code class=\"language-bash\">sudo dnf -y install nginx || sudo yum -y install nginx\nsudo systemctl enable --now nginx\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; A running service you can later use to sanity-check the host.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\nCheck service status:<\/p>\n\n\n\n<pre><code class=\"language-bash\">systemctl status nginx --no-pager\n<\/code><\/pre>\n\n\n\n<p>If your security list allows inbound TCP\/80 and you have a public IP, you can test from your laptop:<\/p>\n\n\n\n<pre><code class=\"language-bash\">curl -I http:\/\/&lt;PUBLIC_IP&gt;\n<\/code><\/pre>\n\n\n\n<blockquote>\n<p>Note: Fleet Application Management discovery may or may not treat nginx as a \u201cdiscoverable application type.\u201d This step is for host realism and connectivity checks, not as a guaranteed discoverable application.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Create an agent install key and download the agent installer (console-driven)<\/h3>\n\n\n\n<p>Fleet Application Management commonly relies on the <strong>OCI Management Agent<\/strong> to connect hosts. The typical onboarding flow is:\n&#8211; create an agent install key in OCI,\n&#8211; download an installer or script,\n&#8211; run it on the host to register the agent.<\/p>\n\n\n\n<p><strong>Console path (typical)<\/strong>: Observability &amp; Management \u2192 Management Agent (or equivalent entry)<br\/>\nFrom there, look for:\n&#8211; Install keys\n&#8211; Download agent\n&#8211; Registration instructions<\/p>\n\n\n\n<p>Because the exact navigation and UI labels can change, follow the current official steps here:\n&#8211; Management Agent documentation: https:\/\/docs.oracle.com\/en-us\/iaas\/management-agent\/home.htm<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You obtain an install script or package and an install key tied to your compartment.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; In the console, you can see the install key exists and is Active (or usable).\n&#8211; You have downloaded the installer bundle or copied the install command.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Install and register the Management Agent on the compute instance<\/h3>\n\n\n\n<p>Run the install command exactly as provided by the OCI console for your install key and OS.<\/p>\n\n\n\n<p>Typical pattern (example only \u2014 <strong>do not copy blindly<\/strong>):\n&#8211; download installer\n&#8211; run as root with key\/parameters\n&#8211; start agent service<\/p>\n\n\n\n<p>Because Oracle may change the installer format, <strong>use the console-generated command<\/strong>.<\/p>\n\n\n\n<p>After installation, check the agent service. One of these patterns is common:<\/p>\n\n\n\n<pre><code class=\"language-bash\">sudo systemctl status oracle-cloud-agent --no-pager || true\nsudo systemctl status managementagent --no-pager || true\nsudo systemctl list-units --type=service | egrep -i \"agent|oracle\" || true\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; The agent is installed and running.\n&#8211; The host registers back to OCI and appears in the Management Agent list.<\/p>\n\n\n\n<p><strong>Verification (console)<\/strong>\n&#8211; Go to the Management Agent list in your compartment.\n&#8211; Confirm the agent\/host shows as <strong>Active<\/strong> (or similar healthy state).\n&#8211; Confirm last heartbeat time updates.<\/p>\n\n\n\n<p><strong>Common error<\/strong>\n&#8211; Agent shows \u201cInactive\u201d or never appears.\n  &#8211; Fix: confirm outbound egress (DNS + HTTPS), confirm system time is correct (NTP), confirm you used the right compartment\/install key.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 7: Create a Fleet in Fleet Application Management<\/h3>\n\n\n\n<p><strong>Console path<\/strong>: Observability &amp; Management \u2192 Fleet Application Management \u2192 Fleets \u2192 Create fleet<\/p>\n\n\n\n<p>Provide:\n&#8211; Name: <code>lab-fleet-1<\/code>\n&#8211; Compartment: <code>lab-fam<\/code>\n&#8211; Tags: optional, but recommended (for example <code>Environment=Lab<\/code>)<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Fleet resource is created.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Fleet appears in the Fleets list with an Active lifecycle state.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 8: Add the managed host to the fleet (association\/onboarding)<\/h3>\n\n\n\n<p>The UI typically provides a way to associate managed hosts\/entities with a fleet.<\/p>\n\n\n\n<p><strong>Console path<\/strong> (conceptual): Fleet Application Management \u2192 your fleet \u2192 Managed hosts \/ Targets \/ Entities \u2192 Add<\/p>\n\n\n\n<p>Select the compute instance\/agent you registered.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Fleet now contains at least one managed host\/entity.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Fleet details show the host in its inventory list.<\/p>\n\n\n\n<blockquote>\n<p>If you do not see the host as selectable: verify compartments (fleet and agent may need to be in accessible compartments) and verify IAM permissions.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 9: Run discovery \/ refresh inventory (if available)<\/h3>\n\n\n\n<p>Fleet Application Management may provide a discovery action, scheduled discovery, or refresh.<\/p>\n\n\n\n<p>In the fleet UI, look for:\n&#8211; Discover applications\n&#8211; Refresh inventory\n&#8211; Run discovery job<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Inventory metadata is refreshed.\n&#8211; If supported application types are present, you may see discovered application instances\/deployments.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; The fleet shows updated timestamps.\n&#8211; Any discovered items appear in application inventory views.<\/p>\n\n\n\n<blockquote>\n<p>If nothing is discovered, it may mean your installed workload isn\u2019t a supported discoverable type. The lab is still successful if the host is managed and the fleet association works.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Validation<\/h3>\n\n\n\n<p>Use this checklist:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Compute instance is reachable<\/strong>\n   &#8211; SSH works and basic commands run:<\/li>\n<\/ol>\n\n\n\n<p><code>bash\n   uname -a<\/code><\/p>\n\n\n\n<ol class=\"wp-block-list\" start=\"2\">\n<li><strong>Agent is healthy<\/strong>\n   &#8211; System service running (name varies):<\/li>\n<\/ol>\n\n\n\n<p><code>bash\n   sudo systemctl --no-pager --full status managementagent || true\n   sudo systemctl --no-pager --full status oracle-cloud-agent || true<\/code><\/p>\n\n\n\n<ol class=\"wp-block-list\" start=\"3\">\n<li>\n<p><strong>Agent appears in OCI<\/strong>\n   &#8211; Management Agent list shows the host as Active\/Healthy.<\/p>\n<\/li>\n<li>\n<p><strong>Fleet exists and includes the host<\/strong>\n   &#8211; Fleet details show the managed host\/entity association.<\/p>\n<\/li>\n<li>\n<p><strong>Inventory refresh\/discovery runs<\/strong> (if available)\n   &#8211; Fleet inventory timestamps update and\/or discovered entities appear.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">Issue: Agent doesn\u2019t show up in OCI<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Check outbound connectivity<\/strong>:<\/li>\n<li>\n<p>DNS resolution works:<\/p>\n<p><code>bash\nnslookup oracle.com || getent hosts oracle.com<\/code><\/p>\n<\/li>\n<li>\n<p>HTTPS outbound works:<\/p>\n<p><code>bash\ncurl -I https:\/\/www.oracle.com<\/code><\/p>\n<\/li>\n<li>\n<p><strong>Check system time<\/strong> (TLS failures often occur with wrong clock):<\/p>\n<\/li>\n<li>\n<p>On Oracle Linux:<\/p>\n<p><code>bash\ntimedatectl<\/code><\/p>\n<\/li>\n<li>\n<p><strong>Review agent logs<\/strong><\/p>\n<\/li>\n<li>\n<p>Log locations vary by agent and version. Use:<\/p>\n<p><code>bash\nsudo journalctl -u managementagent --no-pager | tail -200 || true\nsudo journalctl -u oracle-cloud-agent --no-pager | tail -200 || true<\/code><\/p>\n<\/li>\n<li>\n<p>If logs are elsewhere, consult the agent docs for your OS.<\/p>\n<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Issue: You can\u2019t add the host to the fleet<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ensure:<\/li>\n<li>The fleet and the host\/agent are in the intended compartment(s).<\/li>\n<li>Your user\/group has permissions in both compartments.<\/li>\n<li>For production, implement explicit IAM policies (verify in docs).<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Issue: Discovery finds no applications<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Confirm:<\/li>\n<li>Your application type is supported by Fleet Application Management discovery in your region.<\/li>\n<li>Required plugins\/collectors are enabled (if the agent uses plugins).<\/li>\n<li>If you need guaranteed \u201cdiscoverable\u201d behavior, use an application type explicitly documented as supported.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Cleanup<\/h3>\n\n\n\n<p>To avoid ongoing charges, delete in this order:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Terminate compute instance<\/strong>\n   &#8211; Compute \u2192 Instances \u2192 <code>fam-lab-vm1<\/code> \u2192 Terminate\n   &#8211; Choose to delete attached boot volume (if you do not need it)<\/p>\n<\/li>\n<li>\n<p><strong>Delete NAT Gateway<\/strong> (if created)\n   &#8211; Networking \u2192 NAT Gateways \u2192 delete<\/p>\n<\/li>\n<li>\n<p><strong>Delete VCN<\/strong> (if created for the lab)\n   &#8211; Networking \u2192 VCNs \u2192 delete (wizard typically deletes dependent resources)<\/p>\n<\/li>\n<li>\n<p><strong>Delete fleet<\/strong>\n   &#8211; Fleet Application Management \u2192 Fleets \u2192 delete <code>lab-fleet-1<\/code><\/p>\n<\/li>\n<li>\n<p><strong>Delete agent install keys<\/strong> (optional hygiene)\n   &#8211; Management Agent \u2192 Install keys \u2192 delete lab keys<\/p>\n<\/li>\n<li>\n<p><strong>Delete compartment<\/strong> (optional, only if empty)\n   &#8211; Remove any remaining resources first.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">11. Best Practices<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Architecture best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Design fleets around ownership and operational boundaries<\/strong>, not purely around technical topology.<\/li>\n<li>Good fleet boundaries: environment (prod\/dev), business unit, SLA tier, compliance boundary.<\/li>\n<li><strong>Use compartments to enforce environment separation<\/strong> and apply IAM and quotas cleanly.<\/li>\n<li>Prefer <strong>private subnets<\/strong> for production hosts; control egress with NAT and allowlists.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">IAM\/security best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>least privilege<\/strong>:<\/li>\n<li>Separate roles: fleet viewers, fleet operators, fleet administrators.<\/li>\n<li>Keep onboarding privileges (agent install keys, registration) restricted.<\/li>\n<li>Use <strong>dynamic groups<\/strong> only when required by your chosen integration; prefer explicit user\/group permissions for administrative actions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Avoid always-on NAT Gateways in small dev environments unless required.<\/li>\n<li>Keep telemetry\/log retention minimal while meeting compliance.<\/li>\n<li>Tag fleets and hosts for cost allocation and chargeback.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Performance best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Validate agent overhead on representative hosts before large-scale rollout.<\/li>\n<li>Stagger discovery\/refresh jobs (if configurable) to avoid thundering herd effects.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Reliability best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Treat agents as part of your production runtime dependencies:<\/li>\n<li>monitor agent health,<\/li>\n<li>automate reinstall\/repair runbooks,<\/li>\n<li>standardize golden images if possible.<\/li>\n<li>Use compartments and tagging to ensure correct scoping when hosts are replaced.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operations best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Centralize operational logs (agent logs, key service logs) with consistent retention.<\/li>\n<li>Establish a naming convention:<\/li>\n<li>Fleets: <code>&lt;App&gt;-&lt;Env&gt;-&lt;Region&gt;<\/code> or <code>&lt;Domain&gt;-&lt;Env&gt;<\/code><\/li>\n<li>Hosts: include environment and role<\/li>\n<li>Create runbooks for:<\/li>\n<li>onboarding\/offboarding hosts<\/li>\n<li>common discovery failures<\/li>\n<li>access review procedures<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Governance\/tagging\/naming best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Mandatory tags (common):<\/li>\n<li><code>Environment<\/code>, <code>Owner<\/code>, <code>CostCenter<\/code>, <code>DataClassification<\/code><\/li>\n<li>Use defined tags with allowed values to prevent drift.<\/li>\n<li>Align fleet design with landing zone guardrails.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">12. Security Considerations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Identity and access model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Users access Fleet Application Management via <strong>OCI IAM<\/strong>.<\/li>\n<li>Use compartments to constrain blast radius.<\/li>\n<li>Prefer separate groups:<\/li>\n<li><code>FAM-Admins<\/code>: create\/delete fleets, configure discovery<\/li>\n<li><code>FAM-Ops<\/code>: day-2 operations<\/li>\n<li><code>FAM-Viewers<\/code>: read-only for auditors\/support<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Encryption<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI control-plane services generally encrypt data at rest and in transit as part of the platform.<br\/>\n  Verify service-specific encryption statements in the official documentation and compliance docs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network exposure<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Managed hosts should not require inbound internet connectivity for agent operation in many designs; outbound egress is more typical.<\/li>\n<li>For production:<\/li>\n<li>keep hosts private,<\/li>\n<li>restrict egress destinations,<\/li>\n<li>avoid broad <code>0.0.0.0\/0<\/code> inbound rules.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secrets handling<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Do not store credentials in scripts or on hosts.<\/li>\n<li>Use <strong>OCI Vault<\/strong> for secrets used by operational tooling around fleets.<\/li>\n<li>Rotate agent-related keys\/tokens per documented procedures.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Audit\/logging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>OCI Audit<\/strong> to track who changed fleet configuration and onboarding keys.<\/li>\n<li>Export audit logs to your SIEM if required.<\/li>\n<li>Collect agent logs centrally to detect tampering or repeated registration failures.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compliance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Map fleets to compliance boundaries:<\/li>\n<li>PCI, HIPAA, SOC2, ISO27001<\/li>\n<li>Apply compartment-level policies and tagging.<\/li>\n<li>Ensure evidence collection:<\/li>\n<li>inventory exports\/screenshots (where accepted),<\/li>\n<li>audit logs,<\/li>\n<li>change records.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common security mistakes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Over-permissioned policies (\u201cmanage all-resources in tenancy\u201d) in production.<\/li>\n<li>Public subnets for production app hosts.<\/li>\n<li>Not monitoring agent health (silent visibility loss).<\/li>\n<li>Long-lived onboarding keys not rotated\/revoked.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secure deployment recommendations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Start with a <strong>pilot<\/strong> compartment and a small set of hosts.<\/li>\n<li>Lock down IAM before scaling.<\/li>\n<li>Use a dedicated subnet\/NSG for managed hosts and standardize egress.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">13. Limitations and Gotchas<\/h2>\n\n\n\n<p>Because capabilities vary by region and supported application types, confirm details in official docs. Common gotchas include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Supported application types<\/strong>: Discovery and management actions typically apply only to specific stacks. If your app type isn\u2019t supported, you may only get host-level association (or nothing beyond agent health).<\/li>\n<li><strong>Region availability<\/strong>: Service may not be available in every region or may have feature differences.<\/li>\n<li><strong>Network requirements<\/strong>: Agent needs outbound connectivity to OCI endpoints; private subnet deployments require NAT or equivalent.<\/li>\n<li><strong>IAM scoping pitfalls<\/strong>:<\/li>\n<li>Fleet in one compartment, agent\/host in another can cause visibility\/association issues.<\/li>\n<li><strong>Agent lifecycle management<\/strong>:<\/li>\n<li>OS upgrades, firewall changes, or certificate\/time drift can break registration.<\/li>\n<li><strong>Telemetry costs<\/strong>:<\/li>\n<li>If you integrate with additional logging\/analytics services, costs can rise quickly.<\/li>\n<li><strong>Operational expectation mismatch<\/strong>:<\/li>\n<li>Fleet Application Management is not the same as deep APM tracing; use OCI APM for request traces and code-level diagnostics.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<p>Fleet Application Management sits in the middle ground between \u201chost management\u201d and \u201cdeep application observability.\u201d Consider what you actually need: inventory, patching, runtime metrics, traces, or configuration management.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Comparison table<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Option<\/th>\n<th>Best For<\/th>\n<th>Strengths<\/th>\n<th>Weaknesses<\/th>\n<th>When to Choose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>OCI Fleet Application Management<\/strong><\/td>\n<td>Fleet-level application inventory\/management in OCI<\/td>\n<td>Fleet grouping, OCI governance (IAM\/compartments), centralized inventory (supported types)<\/td>\n<td>Discovery\/actions depend on supported app types; region\/feature variability<\/td>\n<td>When you need application estate inventory and fleet operations in OCI<\/td>\n<\/tr>\n<tr>\n<td><strong>OCI Application Performance Monitoring (APM)<\/strong><\/td>\n<td>Performance tracing and diagnostics<\/td>\n<td>Distributed tracing, service maps, app-centric diagnostics<\/td>\n<td>Not primarily an inventory\/CMDB tool; requires instrumentation<\/td>\n<td>When you need deep performance visibility and traces<\/td>\n<\/tr>\n<tr>\n<td><strong>OCI Logging \/ Logging Analytics<\/strong><\/td>\n<td>Centralized logs and log analytics<\/td>\n<td>Flexible ingestion, search, retention, dashboards (service-dependent)<\/td>\n<td>Cost can scale with ingestion\/retention; doesn\u2019t inherently model \u201cfleets\u201d<\/td>\n<td>When logs are your primary operational signal<\/td>\n<\/tr>\n<tr>\n<td><strong>OCI OS Management Hub<\/strong><\/td>\n<td>OS patching and package lifecycle<\/td>\n<td>Patch compliance, scheduling, OS\/package inventory<\/td>\n<td>Focused on OS-level, not app-level modeling<\/td>\n<td>When your main goal is OS patching\/compliance at scale<\/td>\n<\/tr>\n<tr>\n<td><strong>Oracle Enterprise Manager (self-managed)<\/strong><\/td>\n<td>Deep enterprise monitoring for Oracle stacks (on-prem\/hybrid)<\/td>\n<td>Mature management for Oracle middleware\/db in many enterprises<\/td>\n<td>Requires infrastructure and admin overhead; separate platform<\/td>\n<td>When you already standardize on Enterprise Manager for enterprise estates<\/td>\n<\/tr>\n<tr>\n<td><strong>AWS Systems Manager<\/strong><\/td>\n<td>Host and application operations on AWS<\/td>\n<td>Mature fleet operations (Run Command, Patch Manager, Inventory)<\/td>\n<td>AWS-specific; not OCI-native<\/td>\n<td>When your fleet is on AWS and you want native tooling<\/td>\n<\/tr>\n<tr>\n<td><strong>Azure Arc + Azure Monitor<\/strong><\/td>\n<td>Hybrid management across clouds\/on-prem<\/td>\n<td>Strong hybrid story; policy integrations<\/td>\n<td>Azure-centric control plane; onboarding overhead<\/td>\n<td>When you\u2019re standardized on Azure for hybrid ops<\/td>\n<\/tr>\n<tr>\n<td><strong>Open-source (Ansible + Prometheus + Grafana)<\/strong><\/td>\n<td>Customizable self-managed operations<\/td>\n<td>Highly flexible; portable<\/td>\n<td>More engineering\/ops burden; governance and inventory are DIY<\/td>\n<td>When you need portability and can run\/operate the stack yourself<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">15. Real-World Example<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Enterprise example: Regulated payments platform on OCI<\/h3>\n\n\n\n<p><strong>Problem<\/strong><br\/>\nA payments company runs 200+ VM-based application instances across dev\/test\/prod compartments. Auditors require evidence of:\n&#8211; where applications run,\n&#8211; who can operate them,\n&#8211; change accountability.<\/p>\n\n\n\n<p><strong>Proposed architecture<\/strong>\n&#8211; Use compartments per environment and compliance boundary.\n&#8211; Create fleets per business capability (Payments, Billing, Risk) and environment (Prod\/NonProd).\n&#8211; Onboard hosts with the management agent.\n&#8211; Centralize audit logs and integrate with Notifications for operational events (where available).<\/p>\n\n\n\n<p><strong>Why Fleet Application Management was chosen<\/strong>\n&#8211; Fleet-first model aligns with enterprise governance.\n&#8211; Integrates with OCI IAM, compartments, and audit.\n&#8211; Provides centralized inventory without building a custom CMDB pipeline.<\/p>\n\n\n\n<p><strong>Expected outcomes<\/strong>\n&#8211; Faster audit evidence generation.\n&#8211; Reduced \u201cunknown application instance\u201d drift.\n&#8211; Clearer separation of duties and reduced over-permissioning.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: SaaS with 20 app servers scaling quickly<\/h3>\n\n\n\n<p><strong>Problem<\/strong><br\/>\nA SaaS startup is growing from 10 to 60 VMs across regions. They don\u2019t want to maintain spreadsheets of which app version runs where.<\/p>\n\n\n\n<p><strong>Proposed architecture<\/strong>\n&#8211; One non-prod and one prod compartment.\n&#8211; Fleets per environment and service boundary.\n&#8211; Tagging for ownership and cost.\n&#8211; Minimal logging retention for cost control.<\/p>\n\n\n\n<p><strong>Why Fleet Application Management was chosen<\/strong>\n&#8211; Centralized inventory and governance with low operational overhead.\n&#8211; Works well with OCI-native patterns.<\/p>\n\n\n\n<p><strong>Expected outcomes<\/strong>\n&#8211; Cleaner operational handoffs as the team grows.\n&#8211; Less time spent tracking deployments manually.\n&#8211; A better foundation for compliance as customers demand SOC2.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<p>1) <strong>Is Fleet Application Management the same as APM?<\/strong><br\/>\nNo. APM focuses on performance telemetry like traces and spans. Fleet Application Management focuses on organizing and managing application estates as fleets (inventory\/management workflows).<\/p>\n\n\n\n<p>2) <strong>Does Fleet Application Management work for any application?<\/strong><br\/>\nNot necessarily. Discovery and actions typically depend on supported application types. Verify supported stacks in the official docs.<\/p>\n\n\n\n<p>3) <strong>Do I need an agent on every host?<\/strong><br\/>\nIn most fleet-style management models, yes\u2014some kind of agent\/collector is typically required to discover inventory and report health. Verify exact requirements in OCI docs.<\/p>\n\n\n\n<p>4) <strong>Can I manage on-prem hosts?<\/strong><br\/>\nPossibly, depending on supported onboarding modes and connectivity requirements. Verify hybrid support in official documentation.<\/p>\n\n\n\n<p>5) <strong>How does access control work?<\/strong><br\/>\nThrough OCI IAM policies and compartments. You can restrict who can view or manage fleets and related resources.<\/p>\n\n\n\n<p>6) <strong>Is Fleet Application Management regional?<\/strong><br\/>\nOCI services often have region-scoped behavior. Verify whether fleet resources and inventory are region-specific in the official docs.<\/p>\n\n\n\n<p>7) <strong>What network ports\/protocols are required?<\/strong><br\/>\nAgents commonly need outbound HTTPS to OCI endpoints. Exact endpoints and ports should be taken from official docs for your agent version and region.<\/p>\n\n\n\n<p>8) <strong>Can I use private subnets?<\/strong><br\/>\nYes, commonly. Provide outbound egress (NAT Gateway or other controlled egress) so the agent can reach OCI endpoints.<\/p>\n\n\n\n<p>9) <strong>How do I troubleshoot agent registration issues?<\/strong><br\/>\nCheck DNS, outbound HTTPS, system time, and agent logs. Confirm you used the correct install key and compartment.<\/p>\n\n\n\n<p>10) <strong>Will it increase my OCI bill?<\/strong><br\/>\nPotentially. Even if the service control plane is low-cost, compute, NAT, data egress, and log storage can add cost. Use the Oracle price list and cost estimator.<\/p>\n\n\n\n<p>11) <strong>Can I automate fleet creation?<\/strong><br\/>\nOften yes via APIs\/SDKs\/CLI if supported. Confirm API availability for Fleet Application Management in the official API reference.<\/p>\n\n\n\n<p>12) <strong>Does it integrate with OCI Events and Notifications?<\/strong><br\/>\nMany OCI services can emit events, but availability varies. Verify Fleet Application Management event types and metrics in docs.<\/p>\n\n\n\n<p>13) <strong>How should I name fleets?<\/strong><br\/>\nUse names that encode ownership and environment, e.g., <code>Payments-Prod<\/code>, <code>Billing-NonProd<\/code>, plus region if needed.<\/p>\n\n\n\n<p>14) <strong>What is the best first production rollout strategy?<\/strong><br\/>\nStart with a pilot: one compartment, one fleet, a small set of hosts, validate IAM and discovery, then expand gradually.<\/p>\n\n\n\n<p>15) <strong>What\u2019s the difference between host management and application fleet management?<\/strong><br\/>\nHost management focuses on OS patching and instance lifecycle. Application fleet management models and groups application instances\/deployments so you can operate at the app boundary.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn Fleet Application Management<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Resource Type<\/th>\n<th>Name<\/th>\n<th>Why It Is Useful<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Official Documentation<\/td>\n<td>Fleet Application Management docs \u2013 https:\/\/docs.oracle.com\/en-us\/iaas\/fleet-application-management\/home.htm<\/td>\n<td>Primary source for current features, concepts, and workflows<\/td>\n<\/tr>\n<tr>\n<td>Official Documentation<\/td>\n<td>Management Agent docs \u2013 https:\/\/docs.oracle.com\/en-us\/iaas\/management-agent\/home.htm<\/td>\n<td>Required for host onboarding and troubleshooting agent issues<\/td>\n<\/tr>\n<tr>\n<td>Official Pricing<\/td>\n<td>Oracle Cloud Price List \u2013 https:\/\/www.oracle.com\/cloud\/price-list\/<\/td>\n<td>Authoritative pricing reference (region\/SKU dependent)<\/td>\n<\/tr>\n<tr>\n<td>Pricing Tool<\/td>\n<td>OCI Cost Estimator \u2013 https:\/\/www.oracle.com\/cloud\/costestimator.html<\/td>\n<td>Estimate end-to-end costs including compute\/network\/logging<\/td>\n<\/tr>\n<tr>\n<td>Free Tier<\/td>\n<td>Oracle Cloud Free Tier \u2013 https:\/\/www.oracle.com\/cloud\/free\/<\/td>\n<td>Understand Always Free limits and eligibility<\/td>\n<\/tr>\n<tr>\n<td>Architecture Center<\/td>\n<td>OCI Architecture Center \u2013 https:\/\/docs.oracle.com\/solutions\/<\/td>\n<td>Reference architectures and best practices (use search for observability\/management patterns)<\/td>\n<\/tr>\n<tr>\n<td>Governance<\/td>\n<td>OCI IAM docs \u2013 https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Identity\/home.htm<\/td>\n<td>Policies, compartments, and least-privilege design<\/td>\n<\/tr>\n<tr>\n<td>Observability<\/td>\n<td>OCI Monitoring docs \u2013 https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Monitoring\/home.htm<\/td>\n<td>Alerts\/alarms patterns that often complement fleet operations<\/td>\n<\/tr>\n<tr>\n<td>Logging<\/td>\n<td>OCI Logging docs \u2013 https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Logging\/home.htm<\/td>\n<td>Central log collection patterns for agents and workloads<\/td>\n<\/tr>\n<tr>\n<td>Community (reputable)<\/td>\n<td>Oracle Cloud customer architecture\/blog resources \u2013 https:\/\/blogs.oracle.com\/cloud\/<\/td>\n<td>Practical posts and updates; validate against official docs<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">18. Training and Certification Providers<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Institute<\/th>\n<th>Suitable Audience<\/th>\n<th>Likely Learning Focus<\/th>\n<th>Mode<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps engineers, SREs, cloud engineers<\/td>\n<td>DevOps practices, automation, cloud ops foundations (verify OCI-specific coverage)<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>ScmGalaxy.com<\/td>\n<td>Beginners to intermediate DevOps learners<\/td>\n<td>SCM, CI\/CD, DevOps fundamentals<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.scmgalaxy.com\/<\/td>\n<\/tr>\n<tr>\n<td>CLoudOpsNow.in<\/td>\n<td>Cloud ops practitioners<\/td>\n<td>Operations, monitoring, cloud management concepts<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.cloudopsnow.in\/<\/td>\n<\/tr>\n<tr>\n<td>SreSchool.com<\/td>\n<td>SREs and reliability-focused engineers<\/td>\n<td>SRE practices, incident management, observability<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.sreschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>AiOpsSchool.com<\/td>\n<td>Ops and platform teams exploring AIOps<\/td>\n<td>AIOps concepts, event correlation, operational analytics<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.aiopsschool.com\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">19. Top Trainers<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Platform\/Site<\/th>\n<th>Likely Specialization<\/th>\n<th>Suitable Audience<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>RajeshKumar.xyz<\/td>\n<td>DevOps\/cloud training content (verify latest topics)<\/td>\n<td>Beginners to working professionals<\/td>\n<td>https:\/\/rajeshkumar.xyz\/<\/td>\n<\/tr>\n<tr>\n<td>devopstrainer.in<\/td>\n<td>DevOps training<\/td>\n<td>Engineers building CI\/CD and ops skills<\/td>\n<td>https:\/\/www.devopstrainer.in\/<\/td>\n<\/tr>\n<tr>\n<td>devopsfreelancer.com<\/td>\n<td>DevOps freelance\/training services (verify offerings)<\/td>\n<td>Teams needing short-term enablement<\/td>\n<td>https:\/\/www.devopsfreelancer.com\/<\/td>\n<\/tr>\n<tr>\n<td>devopssupport.in<\/td>\n<td>DevOps support\/training resources (verify offerings)<\/td>\n<td>Ops teams needing troubleshooting support<\/td>\n<td>https:\/\/www.devopssupport.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">20. Top Consulting Companies<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Company<\/th>\n<th>Likely Service Area<\/th>\n<th>Where They May Help<\/th>\n<th>Consulting Use Case Examples<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>cotocus.com<\/td>\n<td>Cloud\/DevOps consulting (verify service catalog)<\/td>\n<td>Implementation support, platform engineering<\/td>\n<td>Landing zone setup, observability rollout planning, governance design<\/td>\n<td>https:\/\/cotocus.com\/<\/td>\n<\/tr>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps consulting and enablement<\/td>\n<td>Training + implementation guidance<\/td>\n<td>Fleet onboarding process design, IaC enablement, ops runbooks<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>DEVOPSCONSULTING.IN<\/td>\n<td>DevOps consulting (verify service catalog)<\/td>\n<td>DevOps process and tooling<\/td>\n<td>CI\/CD modernization, monitoring strategy, operational maturity improvements<\/td>\n<td>https:\/\/www.devopsconsulting.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">21. Career and Learning Roadmap<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn before Fleet Application Management<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI fundamentals:<\/li>\n<li>compartments, VCNs, subnets, routing, security lists\/NSGs<\/li>\n<li>IAM basics:<\/li>\n<li>groups, policies, dynamic groups, least privilege<\/li>\n<li>Linux basics:<\/li>\n<li>services (<code>systemctl<\/code>), logs (<code>journalctl<\/code>), networking<\/li>\n<li>Observability basics:<\/li>\n<li>metrics vs logs vs traces; alerting fundamentals<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after Fleet Application Management<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI Monitoring + Alarms: operational alerting<\/li>\n<li>OCI Logging and (optionally) Logging Analytics: centralized troubleshooting<\/li>\n<li>OCI Events + Functions: automation for common operational tasks<\/li>\n<li>OS Management Hub: OS patch compliance at scale<\/li>\n<li>IaC with Terraform\/Resource Manager: standardized provisioning and drift control<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Job roles that use it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Engineer \/ Cloud Operations Engineer<\/li>\n<li>DevOps Engineer<\/li>\n<li>Site Reliability Engineer (SRE)<\/li>\n<li>Platform Engineer<\/li>\n<li>Security Engineer (governance and auditability)<\/li>\n<li>Solutions Architect (operational architecture design)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>Oracle certification offerings change over time. Check current OCI certification paths here:\n&#8211; https:\/\/education.oracle.com\/<\/p>\n\n\n\n<p>Look for certifications related to:\n&#8211; OCI Foundations\n&#8211; OCI Architect \/ Operations tracks\n&#8211; Observability\/Management topics (if offered)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Build a multi-compartment lab (dev\/prod) and implement fleet separation with least privilege.<\/li>\n<li>Onboard 5\u201310 hosts and standardize tags, naming, and access roles.<\/li>\n<li>Create a runbook for agent failures and implement centralized agent log collection.<\/li>\n<li>Integrate alarms\/notifications for operational signals relevant to your fleet.<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">22. Glossary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OCI (Oracle Cloud Infrastructure)<\/strong>: Oracle Cloud\u2019s IaaS\/PaaS platform.<\/li>\n<li><strong>Observability and Management<\/strong>: OCI category covering monitoring, logging, and operational services.<\/li>\n<li><strong>Fleet<\/strong>: A logical group used to manage multiple application instances\/deployments together.<\/li>\n<li><strong>Compartment<\/strong>: An OCI governance boundary for organizing and isolating resources.<\/li>\n<li><strong>IAM Policy<\/strong>: A rule that grants permissions in OCI (who can do what in which compartment).<\/li>\n<li><strong>Managed host\/entity<\/strong>: A server\/instance connected to OCI for inventory\/management.<\/li>\n<li><strong>Management Agent<\/strong>: Host-based agent used to connect workloads to OCI management services (exact usage depends on service and configuration).<\/li>\n<li><strong>NAT Gateway<\/strong>: Provides outbound internet connectivity for private subnet resources without exposing them to inbound internet traffic.<\/li>\n<li><strong>Audit log<\/strong>: OCI record of control-plane actions for governance and forensics.<\/li>\n<li><strong>Tags (defined\/freeform)<\/strong>: Metadata used for governance, search, and cost allocation.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p>Fleet Application Management in <strong>Oracle Cloud<\/strong> (under <strong>Observability and Management<\/strong>) helps you manage applications at scale using a <strong>fleet-based model<\/strong>: discover supported application inventory on connected hosts, group assets into fleets, and operate with OCI-native governance (compartments, IAM, tags, audit).<\/p>\n\n\n\n<p>It matters because operational complexity grows faster than infrastructure count. Fleets give you a practical structure for inventory, change planning, and access control\u2014especially in multi-environment, multi-team organizations.<\/p>\n\n\n\n<p>Cost-wise, the main drivers are usually <strong>compute<\/strong>, <strong>network egress\/NAT<\/strong>, and any additional <strong>logging\/telemetry retention<\/strong> you enable. Security-wise, success depends on <strong>least privilege IAM<\/strong>, controlled egress for agents, and strong compartment\/tag governance.<\/p>\n\n\n\n<p>Use Fleet Application Management when you need <strong>centralized application estate visibility and fleet operations<\/strong> in OCI. If your priority is deep performance tracing, choose <strong>OCI APM<\/strong> instead, and if you mainly need OS patching, consider <strong>OS Management Hub<\/strong>.<\/p>\n\n\n\n<p>Next learning step: review the official Fleet Application Management docs and validate which application types are supported in your region, then build a small pilot fleet in a dedicated compartment:\n&#8211; https:\/\/docs.oracle.com\/en-us\/iaas\/fleet-application-management\/home.htm<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Observability and Management<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[75,62],"tags":[],"class_list":["post-955","post","type-post","status-publish","format-standard","hentry","category-observability-and-management","category-oracle-cloud"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/955","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=955"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/955\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=955"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=955"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=955"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}