Status Report
The agent web interface’s Status page (View > Status) shows information about the current status of the agent. You can also view it with the view status command in the Agent Telnet Interface. In the following, the different parts of the report are described.
General section
Section titled “General section”Started at Fri Mar 26 20:49:49 2024Configurated at Fri Mar 26 20:49:49 2024Configured 4 timesProtocol Version 830Encryption mode 128 bit AESLast delivery Thu Apr 01 19:35:04 2024Backend connections 2836Failed connections 0Agent mode Normal| Line | Description |
|---|---|
| Started at | The date and time that the agent executable was invoked. |
| Configurated at | The date and time that the agent was configured. Very often this is the same as the time the agent was started, but if a new configuration has been received (or the agent has been manually reconfigured), the two times will be different. |
| Configured | The number of times that the agent has been configured. |
| Protocol Version | A number that identifies the protocol that the agent uses for communication with the collector process. An 8.3 agent starts with protocol version 830 and then uses the version that it negotiates with the server. |
| Encryption mode | No encryption or 128 bit AES |
| Last delivery | Date and time of the last successful communication with the server collector process. |
| Backend connections | The number of successful communications with the server collector process since the agent was last started. |
| Failed connections | The number of unsuccessful communication attempts with the server collector process. |
| Agent mode | Normal, or suspended if the agent has been suspended. |
Thread status
Section titled “Thread status”The second section, Running Threads, is a table with one row for each thread inside the agent. The columns are:
| Column | Description |
|---|---|
| Id | The Windows thread ID. |
| Name | The name of the thread. |
| Start | The date and time that the thread was started. |
| State | Running or Idle. |
| Usage % | How much of the time the thread has been running. |
| Wait Time (Sec) | For an idle thread, how long it has been waiting. |
| Run Time (Sec) | How long the thread has been running in total. |
The following thread names may appear in the list:
| Thread Name | Description |
|---|---|
| E2EAppRequestReport | Dispatches application pings, and manages application ping reports. |
| E2EBackEndConnection | Handles communication with the server collector process. |
| E2ECitrixReports | Collects Citrix data and manages the session and QoS data reports. |
| E2EDynamicMachine | Collects dynamic machine data and process data, and manages the related reports for operating systems that support process performance data. |
| E2EReportIntervalRunner | Timer thread that controls delivery and trashing of data. |
| E2ETagEngine_Http | Runs the pattern matching that finds tags in http TCP/IP packets, and manages the related reports. |
| E2ETcp | Processes incoming TCP/IP and UDP/IP packets, distributes packets for tag processing, and manages the network reports. |
| E2EWebRequest | Runs a single HTTP-based application ping. |
The agent checks its threads regularly and restarts itself if a thread stops responding. See Multi Threaded Service.
Below the thread list, the report can show time-stamped notes that the agent adds while it runs, for example about the Citrix library that it has loaded.
Last application ping
Section titled “Last application ping”Last Network Application Ping Request:
Thu Apr 01 20:25:01 2024Application=httpNappId=999Iterations=1Delay=0www.example.comThis is the exact content of the latest received (or locally stimulated) network application ping request that the agent has processed.