Managing Agent Configurations

To publish custom metrics using an agent configuration, an instance must be in a dynamic group, and that dynamic group must be allowed to manage agent configurations and to use metrics.

1. Install the agent.

2. Verify that the agent is installed.

3. Define a dynamic group for the resource or resources.

   Example matching rules:

   To specify an instance by ID:

   All {instance.id = 'ocid1.instance.<region>.<location>.<unique_ID>'}

   To specify all instances in a compartment:

   All {instance.compartmentid = 'ocid1.compartment.<region>..<unique_ID>'}

4. Grant permissions to the dynamic group to manage agent configurations, and to use agent configurations to publish custom metrics to a metric namespace.

   Example policy:

   Allow dynamic-group <group_name> to use metrics in tenancy 
   Allow dynamic-group <group_name> to manage unified-configuration in tenancy 

5. Set up an input for the agent configuration.

   For example, expose metrics from a virtual machine (VM) using an HTTP endpoint in Prometheus format:

   http://1.2.3.4:9100/metrics

The following pages describe agent installation and verification:

• Installing the Agent
• Verifying Agent Installation

The following pages describe how you can manage agent configurations:

• Creating an Agent Configuration
• Listing Agent Configurations
• Getting an Agent Configuration's Details
• Updating an Agent Configuration
• Moving an Agent Configuration to a Different Compartment
• Tagging an Agent Configuration
  • Tagging an Agent Configuration at Creation
  • Tagging an Agent Configuration When Updating
• Disabling an Agent Configuration
• Enabling an Agent Configuration
• Deleting an Agent Configuration

Following are the operating systems (OSs) supported by agent configurations: