Agent Management

This page describes how to use the Agent Management console, which is a user interface page that can be used to view the active Splunk AppDynamics agents and collectors in your environment. An agent or collector is considered active if it has synced with the Cisco Observability Platform within the past 5-10 minutes.

This console currently only displays Kubernetes® agents.

Before You Begin

To view the Agent Management console, you must have one of the following Tenant roles: Config Manager or Troubleshooter. See Assign Roles for Tenants.
If your agents and collectors are < 24.1.0, you must upgrade them to view them on the Agent Management console. See Upgrade Operators and Collectors.

View the Agent Management Console

The agent management console can be accessed through the Cisco Observability Platform or Cisco Cloud Observability.

To view all of the active agents in your Cisco Observability Platform environment:

Log into the Cisco Observability Platform.
In the left-hand navigation panel, click Tools > Agent Management.

To view the active agents in your Cisco Cloud Observability environment:

Log into the Cisco Observability Platform.
In the banner, click Platform Home > Cisco Cloud Observability.
In the left-hand navigation panel, click Tools > Agent Management.

Use the Agent Management Console

The data for the Namespace, Deployment Name, Deployment Type, Pod Name, and Smart Agent Version columns is derived from the Smart Agent that is managing the cluster.

You can interact with the user interface as follows:

Action	Description
View the Collector Types column	View the count of different collector types in a particular cluster.
Click the column header.	Sort the column in ascending or descending order.
Click the arrow icon next to the Cluster Name.	Open a table that displays a list of the collector type(s) and number of collectors of each type in a cluster.
Click on a row.	Open the Inspector panel, which displays additional metadata about the selected cluster.

Third party names, logos, marks, and general references used in these materials are the property of their respective owners or their affiliates in the United States and/or other countries. Inclusion of such references are for informational purposes only and are not intended to promote or otherwise suggest a relationship between Splunk AppDynamics and the third party.