The Agents Overview dashlet provides information on the Agents registered on the AppMon Server, including their properties and deployed sensors.
Access the Agents Overview dashlet the following ways:
- In the Cockpit sidebar, click Agents Overview from the Status Overview node. In this case the dashlet displays all the agents, connected to the server. Note the global icon in the dashlet header.
- In the Monitoring Overview dashboard, click the gear icon and select Agents Overview from the menu. In this case the dashlet displays only the agents, related to the System Profile.
The dashlet has two main sections. The Agent list shows all Agents that are registered on the connected Server. Below this section the Details pane provides information about the selected Agent.
When the cursor is in the dashlet, the toolbar appears at the top left corner. It provides the following functions:
- Show offline Agents: List Agents that once were connected to a System Profile but are no longer connected. Offline Agents are removed automatically after 72 hours.
- Agents: This is the default table view, shown in the previous figure. The Agents are listed in alphabetical order.
- Logical Hierarchy: Agents are organized by System Profile and Agent Group.
- Physical Hierarchy: Agents are organized by Collector to which they are connected.
- Details: Show or hide the Details pane at the bottom of the dashlet.
|The Agent is connected and up to date.|
|The Agent is not connected.|
|There is a problem with the Agent, for example it does not match any System Profile. To get more information, right-click the Agent and click Details.|
|The application monitored by the application must be restarted to get the most recent Agent version injected.|
|he Agent is outdated and is not bootstrapped. You need to manually configure the Agent to use the current Agent library.T|
|The Agent is connected to an outdated AppMon Collector. You need to restart the Collector.|
|The Agent does not match the rollout criteria of the controlled update rollout. Therefore, it is not updated (see Product Updates for further details).|
|The agent is not updated after a restart because automatic Agent Updates are disabled.|
The columns in the Agent list vary depending on the selected view. Most column widths can be adjusted, but you may need to scroll right to view all columns.
|Name||Agents||List of agents in alphabetical order. The presented icon symbolizes the state of the agent (see previous table).
Depending on the technology type, supplemental data, such as the version or app name pool, is appended to the user-defined agent name in brackets.
For example, Apache 2.2 is automatically appended after the agent name dtwsagent, as shown in the following agent name example:
|Logical Hierarchy||System Profile > Agent Group > Agent tree.|
|Physical Hierarchy||Collector > Agent tree.|
|Host||all||The host to which the Agent is connected.|
|Connection State||all||This column, to the right of the Hosts column, does not have a heading. It displays an icon that indicates the Agent's connection state.|
|System Profile||Agents Physical Hierarchy||The System Profile used by the Agent.|
|Agent Mapping||all||The configuration of the System Profile used by the Agent.|
|Agent Group||Agent Physical Hierarchy||The Agent Group into which the Agent is mapped.|
|Technology Type||all||This column, to the right of the Agent Group column, does not have a heading. It lists the technology type: Java or .NET.|
|Version||all||The AppMon version: major.minor.revision.build.|
|Bootstrapped||all||The value is true if the Agent is bootstrapped, otherwise false.|
|License||all||Indicates whether the license is valid.|
|Started||all||The date and time the Agent was started.|
|Event Count||all||Number of events sent by the Agent so far.|
|Class Load Count||all||Number of classes loaded by the JVM or CLR associated with the Agent.|
|Total Class Load Count||all||Number of classes loaded by the associated JVM or CLR since startup.|
|Total PurePath Count||all||Number of PurePaths recorded by the Agent.|
|Total Execution Time||all||Total execution time in milliseconds for all instrumented methods.|
|Total CPU Time||all||Total CPU time in milliseconds for all instrumented methods.|
|Connected||all||The value is true if the Agent is connected, otherwise false.|
|Capture||all||The value is true if capturing is enabled, or false if it is disabled.|
|Total Skipped Events||all||Total number of events that were skipped because the Agent's saturation threshold was exceeded.|
|Skipped PurePaths||all||Total number of PurePaths that were skipped because the Agent's saturation threshold was exceeded.|
|Collector||all||Name of the Collector to which the Agent is connected.|
|Data Sent||Physical Hierarchy||Data sent to the Collector, in Bytes per second.|
|Data Received||Physical Hierarchy||Data received from the Collector, in Bytes per second.|
|MPS||all||Average number of nodes collected per second.|
|Average PurePaths Length||all||Average length of all the PurePaths stored in memory.|
|Completed PurePaths||all||Number of completed PurePaths per interval.|
|Skipped Events||all||Average number of skipped events per interval.|
|Send Buffer Queue Used||Logical Hierarchy Physical Hierarchy||Size of the Send Buffer Queue, in megabytes.|
|Send Buffer Queue Committed||Logical Hierarchy Physical Hierarchy||Number of megabytes committed for the Send Buffer Queue.|
|Agent ID||Logical Hierarchy Physical Hierarchy||The unique identifier for the Agent on the AppMon Server.|
Show agent log file
You can access an Agent's log file directly from the Agents Overview by right-clicking the Agent and selecting Show Agent Log File from the context menu. The System Information Dashlet dashlet is added to the dashboard and the first log file of the selected agent is automatically displayed. For sub-agents, this command also opens also the first log file of the parent agent. The log files of any sub-agent are also stored within the log files of their parent agents.
Because the first log file in the System Information Dashlet tree displays, you may need to manually search the tree for the desired log file. It should be found within the same hierarchy level as the opened file.
Restart host agents from client
After an upgrade or patch, you must restart your Host Agents. You can perform the restart from the AppMon Client. Host Agent restarts are limited to three tries every 30 seconds, to prevent an erroneous infinite loop.
For any Agent that is at an AppMon version earlier than 5.5, this feature is not implemented by the auto-update. You must manually upgrade the Agent to use this feature.
Host Agents can be restarted from the Client on all supported platforms. The running Host Agent process keeps its PID. Windows Services are not informed about the internal restart.
Only a user with the Administrator role can use the Host Agent restart function.
- Select one or more Host Agent(s) in the Agent Overview dashlet.
Selected Agents that are not Host Agents are not affected by the restart mechanism, so, you if you want to restart all Host Agents you can just select all the Agents.
- Right-click and select Restart Host Agents from the context menu.
- When prompted, confirm the restart.
The Agent Details section contains tabs to list values for the Agent Properties of the selected Agent and information about the Deployed Sensors of the selected Agent.
This tab provides detailed information about the environment of the AppMon Agent currently selected in the Agents table.
This tab provides information about the instrumented methods for the selected AppMon Agent instance.
- Method: The method name.
- Class: The name of the class containing the method.
- Arguments: Argument types of the method.
- Returns: Return type of the method.
- Api: API(s) assigned to the method.
- Sensor: Sensor(s) applied to the method.
- Flags: Access modifiers for this method
- Pub = public
- Pro = protected
- Pri = private
- Sta = static
- Nat = native
- Fin = final
- Syn = synchronized
- Str = strict
- Source File: Name of the source file that contains the method.
- Line Number: Line number of the method within the source file.
Through the Deployed Sensors tab, you can view decompiled versions of the instrumented classes. To view the decompiled code of a class, right-click the method and select the appropriate item on the Source Lookup cascading menu:.
- Open in IDE: Display the source code in Eclipse or Visual Studio. Only available if the appropriate Plugin is installed. See Eclipse Integration Plugin and Visual Studio Extension.
- Decompile Byte Code: Open a view that displays the byte code representation of the selected method.
- Decompile Source Code: Open a view that shows the source code representation of the selected method. Only available if JAD decompiler is installed.
- Decompile mixed: Open a view that shows a mixed representation, containing both byte code and source code of the selected method. Only available if JAD decompiler is installed.
- Save Byte Code: Save the byte code of the class containing the selected method. Only available if JAD decompiler is installed.
- Open in Reflector: Open the decompiled IL Code in the .NET Reflector. Only available if .NET Reflector is installed.
The original byte code is saved and used for decompiling, so no instrumentation code is visible.
You can use the commands on the Add Sensor Rules cascading menu to define Sensor rules for the selected methods:
- Refine with Callee Methods: All methods that are called by the selected methods are retrieved and can be used as input for new Inclusion Sensor Rules.
- Exclude Selected Methods: All selected methods can be used as input for new Exclusion Sensor Rules.
- Include Selected Methods: All selected methods can be used as input for new Inclusion Sensor Rules.