Fleets in Fleet Application Management

A fleet in Fleet Application Management is a collection or grouping of resources based on criteria. You can define the criteria during fleet creation.

Grouping resources within a fleet enables Fleet Application Management to effectively oversee the lifecycle of these resources within a specified timeframe. This grouping operates under a unified framework defined by attributes you select, such as the products involved in maintenance, the type of environment undergoing maintenance, or applications that require maintenance across various environments. The maintenance activities can run in a staged approach, wherein the maturity level of each environment type dictates the order of maintenance tasks. This categorization allows environments to be classified as development, testing, or production, thus deciding their capacity to accommodate downtime if needed.

When you create a fleet, Fleet Application Management attaches relevant tagging information to the resources within fleets, if Tagging is enabled during the Fleet Application Management onboarding process. The tagging information helps you draw inferences about cost tracking, budgeting, logging, and auditing. Also, tagging information helps organize and search resources. To learn more about Tagging, see Overview of Tagging. For an example of how Tagging information in Fleet Application Management can help, see Examples of Using Tagging Information.

Fleet States

A fleet can have the following states in Fleet Application Management:
  • CREATING: The fleet is being created. When a fleet is in this state, you can't update or delete it. Wait till the fleet reaches the ACTIVE or FAILED state before you try to modify it or delete it.
  • UPDATING: The fleet's settings are being updated, resources are being added. The fleet isn't available for modification in this state. It moves back to the ACTIVE state after the update, or it might move to the FAILED state.
  • ACTIVE: The fleet is active and available for lifecycle operations. When a fleet is in this state, you can modify or delete it.
  • FAILED: A fleet action has failed and the fleet can't be used.
  • DELETING: The fleet is being deleted. You can't modify it.
  • DELETED: The fleet has been deleted. You can't modify it. Fleet Application Management removes deleted fleets after some time.
Fleet resources can have the following states:
  • VALIDATING: The fleet's resources are currently being assessed for validation. After successful validation, the resource transitions to the DISCOVERING state. If validation fails, the resource transitions to either the FAILED or INVALID state, and you're prompted to retry validating the fleet resources. See Validating a Fleet.
  • INVALID: The fleet's resources can't be validated, are stopped, or can't be identified.
  • VALIDATED: The fleet's resources were successfully validated.
  • DISCOVERING: The fleet's resource targets are identified during discovery, transitioning to various progress states such as In Progress, Accepted, Submitted, Failed, and more. If discovery fails, the resource moves to the FAILED state, and you're prompted to retry discovering the fleet resource targets. See Retrying Target Discovery.
  • ACTIVE: Denotes the readiness of the resources to be managed for any product-based lifecycle operations if the validation and discovery of these resources are successful.

Examples of Using Tagging Information

The following examples explain how Tagging information can be helpful for budgeting, tracking spending and costs, searching logs, and checking audit logs in your tenancy.

Suppose you create a fleet by associating it with a specific product with the fleet name, MyProductFleet. If Tagging was enabled during the Fleet Application Management onboarding process, Fleet Application Management adds the following defined tags to fleet resources using the Oracle$FAMS-Tags namespace:

  • Oracle$FAMS-Tags.FleetName: MyProductFleet
  • Oracle$FAMS-Tags.FAMSManaged: Y

Create a Budget

Create a budget by using Oracle$FAMS-Tags and review it.

  1. Open the navigation menu  and select Billing & Cost Management. Under Cost Management, select Budgets.
  2. On the Budgets page, select Create Budget.
  3. Enter a name for the budget, for example, FAMSManagedFleets.
  4. Enter a description for the budget, for example, Budget monitoring for FAMSManagedFleets. Avoid entering confidential information.
  5. Under Budget Scope, select Tags.
  6. For budgets that target a cost-tracking tag:
    1. Select a tag namespace, for example, Oracle$FAMS-Tags.
    2. Select a target cost-tracking tag key, for example, FAMSManaged.
    3. Enter a value for the cost-tracking tag, for example, Y.
  7. Under Schedule, select Monthly for a recurring budget.
    1. In the Budget Amount field, enter a monthly amount for the budget.
    2. In Day of the month to begin budget processing, select a day of the month when you want budget processing to start periodically each month, for example, 1.
  8. Select Create.
To learn more about OCI budgeting and managing budgets, see Budgets Overview.

Track Spending

Track your OCI spending by using cost analysis to view the chart data items using Oracle$FAMS-Tags.

  1. Open the navigation menu  and select Billing & Cost Management. Under Cost Management, select Cost Analysis.
  2. From Start/End Date (UTC), select a time period, for example, Aug 1, 2025 through Aug 7, 2025.
  3. From Granularity, select Daily.
  4. From Show, select Cost.
  5. From Filters, select a filter such as Tag: Oracle$FAMS-Tags.FAMSManaged: Y.
  6. From Grouping dimensions, select Service.
  7. To apply the changes and reload the chart and table with the selected filters, select Apply.
You can save the filtered data as a report that you can view later alongside the predefined reports. See Saving Reports. You can also download the cost details data for further investigation. See Downloading your Cost Details Data. For more information about the cost analysis tool, see Cost Analysis Overview.

Search Logs

Search logs by using the Logging Search page with Oracle$FAMS-Tags.

  1. Open the navigation menu  and select Observability & Management. Under Logging, select Search.
  2. In Custom filters, start typing to display filter settings along with operators. For example: data.definedTags={"FAMSManaged":"Y","FleetName":"MyProductFleet"},"Oracle-Tags":
  3. In Select logs to search, ensure that the compartment is the one from which the resources are added to a fleet. The root compartment is selected by default for filtering.
The logging data in the Explore and Visualize tabs is reloaded according to the filter settings, or you can select Search to apply the filter. To learn more about searching logs using the Logging Search page, see Logging Search.

Check Audit Logs

Explore audit logs using Oracle$FAMS-Tags.

  1. Open the navigation menu  and select Observability & Management. Under Logging, select Audit.
    The list of audit logs for the current compartment is displayed.
  2. Select a compartment from which the resources are added to a fleet.
  3. In Custom filters, start typing to display filter settings along with operators. For example: data.definedTags={"Oracle$FAMS-Tags":{"FAMSManaged":Y","FleetName":"MyProductFleet"},"Oracle-Tags"}}
  4. Select Apply.
For more information about audit logs, see Audit Logs.