Status Report
The agent web interface’s Status page (View > Status) shows information about the current status of the agent. 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 2004Configurated at : Fri Mar 26 20:49:49 2004Protocol Version : 310Last delivery : Thu Apr 01 19:35:04 2004Backend connections : 2836Failed connections : 0| 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. The protocol version defaults to 130, and will stay there until a higher version number has been negotiated with a server. Protocol 130 thus indicates an unconnected agent. |
| 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. |
Thread Status
Section titled “Thread Status”The second section is similar to the following:
1552 E2EBackEndConnection 0x00c611c8 Thu Apr 01 19:59:48 2004 Running1560 E2EReportIntervalRunner 0x00cd3788 Thu Apr 01 19:59:48 2004 Running1572 E2EAppRequestReport 0x00cd2740 Thu Apr 01 19:59:47 2004 Running1576 E2ETcp 0x00c62478 Thu Apr 01 19:59:47 2004 Running1584 E2ETagEngine_Http 0x00c62998 Thu Apr 01 19:59:47 2004 Running1552 E2EBackEndConnection 0x00c611c8 Thu Apr 01 19:59:48 2004 Running1560 E2EReportIntervalRunner 0x00cd3788 Thu Apr 01 19:59:48 2004 Running1572 E2EAppRequestReport 0x00cd2740 Thu Apr 01 19:59:47 2004 Running1576 E2ETcp 0x00c62478 Thu Apr 01 19:59:47 2004 Running1584 E2ETagEngine_Http 0x00c62998 Thu Apr 01 19:59:47 2004 Running
This is a list of the threads inside the agent that are currently running. 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. |
GUARDagentD.exe caused a EXCEPTION_ACCESS_VIOLATION in module GUARDagentD.exe at 001B:0047E2F7Last Application Ping
Section titled “Last Application Ping”Last Network Application Ping Request:
Thu Apr 01 20:25:01 2004Application=httpNappId=999Iterations=1Delay=0www.cnn.dkThis is the exact content of the latest received (or locally stimulated) network application ping request that the agent has processed.