Adding an Agent Type
New Agent Types can be added to the Apica Fleet through a Git Repository. For Apica Fleet Management to work, it is necessary that the agent's process can be controlled by the Apica Fleet's Agent Manager. The agent manager is a sidecar process, which allows the Fleet Control Plane to control the runtime of different agents. Agents Manager can also relay health and configuration changes to the Fleet Control Plane.
The Agent Type configurations are placed within the agent_types directory. A YAML file is used for each agent type to specify its configuration.

The following is an example YAML file for the Prometheus agent.
agent_type_id
string
Unique identifier for the agent type.
description
string
This field is used as a Name for the agent_type.
icon
string
Base64 encoding of the svg icon
manager_defaults
map[string]ManagerDefaults
Default configurations per platform (linux and windows).
The following are the details for the manager_defaults within the platform(linux/windows) field:
config_file
string
Path to the agent’s configuration file.
package_dir
string
Directory where agent-manager is stored.
auto_update
bool
Whether the agent-manager should auto-update.
agent
ManagerAgent *
Detailed agent configuration.
The following are the details for the agent field:
agent_type
string
Same as agent_tyep_id
platform
string
Target platform.
executable
string
Path to the agent binary.
args
[]string
Command-line arguments passed to the agent.
instance_id_file
string
File path where the instance ID is stored.
auth_token_file
string
File path for the agent’s authentication token.
version_command
string
Command to retrieve the agent version.
default_package_assignments
[]string
List of default packages assigned to the agent.
default_config_assignments
[]string
List of default configuration assignments for the agent.
Last updated
Was this helpful?