1. Click Create Fleet.
   Enter the following information to describe the new fleet:

   Fleet name	Give the fleet a name (or accept the default). This name must be unique. For example,''Production Fleet".
   Fleet description	Give the fleet a description. For example, "This fleet groups all the production servers."

2. If you want to enable advanced features in the fleet, select the Enable advanced features option. See Advanced Features for more information.
3. Deselect the Create new operation log option if you don't want operation logs for this fleet. Operation logs are necessary for auditing the logs related to operations carried out in the fleet by JMS. Operation logs might incur additional costs.
4. (Optional) Click Show advanced options to provide one or more tags for the new fleet.
   • In the Tag Fleet section, provide a list of one or more unique tag key-value pairs to describe the fleet. (To edit these later, see Updating a Fleet.)
   • To add more tags, click + Another Tag and then provide the key-value pair for an additional tag.
5. Click Next. You're prompted to review the fleet information, log configuration, and management agent configuration. Inventory logs are created by default as they're needed to store the data related to usage tracking and inventory.

   Click Save as Stack to save these configurations as an Oracle Cloud Stack. See Getting Started with Oracle Cloud Stack.

   (Optional) Click Previous if you want to modify your choices.

6. Click Create. This creates:
   • A new fleet using the information you provided.
   • The management agent install key with unlimited installations and without expiry. The install key will have the same name as the name of the fleet.
   • The jms namespace and fleet_ocid tag key; if these are missing in your tenancy.
   • Log configuration with the following log group information:
     • The log group will be named: JMS_<FleetName>_Log_group
     • Inventory log object will be: <FleetName>_Inventory_log
     • If you've chosen to create an operation log object, then it will be named: <FleetName>_Operation_log

   See Log Configuration Details in the Fleet Properties Tab to view more details.

   Note
   
   JMS creates a log object with a default retention period of one month. To keep the data indefinitely, you can create a Connector Hub connection between the log object and the object storage bucket.
7. Download the installation script from the Install a management agent section. Follow the instructions in Using Installation Script section to install the management agent on your host(s). You can also download the scripts at a later date, when viewing the details of a fleet (see Viewing a Fleet).

You can modify an existing fleet by updating the name and description, enabling or disabling advanced features in the fleet, moving it to a different compartment, and editing its tags.

• Click Edit properties to modify the name of the fleet and its description. Renaming the fleet will rename the underlying log objects, as well.
  • The log group will be: JMS_<FleetName>_Log_group
  • Inventory log object will be: <FleetName>_Inventory_log
  • Operation log object will be: <FleetName>_Operation_log.

  You can also enable or disable Advanced Features from this window.

• Click Move Fleet to move the fleet to a different compartment. See Moving a Fleet.
• Click Add Tags to add tag key-value pair(s) to describe the fleet in its role as an OCI resource.
  These tags describe the fleet in its role as an OCI resource and have no effect on the contents of the fleet.
• To edit or remove a fleet's tags, select the Tags tab and click Edit .
  These tags describe the fleet in its role as an OCI resource and have no effect on the contents of the fleet.

Moving a fleet shifts the fleet from one compartment to another.

1. In the fleet dashboard, select the fleet you want to move from the list.
2. In the fleet details page, click Move Fleet.
   Move fleet to a different compartment dialog opens.
3. Choose new compartment from the list.
4. Click Move Fleet.
   The fleet will be moved to the new compartment.

   Note
   
   If you attempt to move a fleet to a compartment for which you don't have authorization, you'll be presented with the error message Authorization failed or requested resource not found.

The fleet is marked as deleted and traffic from managed instances is ignored by the fleet. (A deleted fleet is kept for 90 days before it is permanently removed.) Deletion has no effect on the managed instances contained by the fleet.

• From More Actions, click Delete to delete the fleet.
  You're prompted to confirm your action.
• Optional: Click the checkbox to permanently delete the associated log configuration. This option is disabled by default. Checking this option deletes underlying log resources. If log resources are removed, you'll not be able to do analytics using the analytics service. If log resources aren't removed, you'll incur storage costs.