Information Sent to the Controller
This table shows the types of information that is collected by an application agent and sent to the Controller.
| Metric | Description |
|---|---|
| Server Request GUID | A unique GUID identifying a request, known as a Business Transaction, in the
form of xxxxxxxx-xxxx-xxxx- xxxx-xxxxxxxxxxxx where
x is a lower-case hexadecimal digit. |
| Application Entry Points | Transaction entry points are identified among various frameworks and technologies. This includes Servlet URIs, Strut Action and Method name, Spring Bean Name and Method Name, JMS queue destination or listener name, Web Service/WCF action/operation name, PHP Virtual Name, and more. |
| Application Exit Points | Transaction exit points are identified among various frameworks and technologies. This includes: HTTP URL end points, JMS queue/destination, type, and vendor; database URL endpoint and vendor/version, web service Service Name, cache name and URL endpoint. |
| Performance Metrics |
In general, for each monitored metric in Splunk AppDynamics, a response time, call rate, and error rate are collected. Each of these metrics also have an automatic baseline derived for each respective metric value. |
| Thread Stack Traces | Code level method execution metrics that comprise the application request are collected. This data includes the class and method that executed and the line number within the source code. Note that less than 5% of transactions will have stack traces collected. Errors/Exceptions and stack trace of error data will be collected. |
| SQL Query Values | If assigned with administrative permissions, SQL query variables within a query can be enabled, collected, and viewed. Note that the parameter data is collected for less than 5% of transactions. Configuration changes are logged in an audit log that is available for security review. |
| Data Collectors | If assigned with administrative permissions, data in the form of HTTP values or method payload can be collected and viewed. Note that a specific data collectors and code payload accessors require explicit configuration to be collected. Note, data is collected for less than 5% of transactions. Configuration changes are logged in an audit log that is available for security review. |
| Hostname | The DNS hostname of the machine (virtual/physical) from where the agent is installed and reporting monitoring data. |
| IP Address Internet Protocol (IP) |
IP Address Internet Protocol (IP) address of the machine (virtual/physical) where the agent is sending monitoring data from. |
| CPU Usage | The value of CPU that is consumed on the monitored machine/virtual machine. |
| Memory Usage | The value of physical memory that is consumed on the monitored/virtual machine. |
| Network I/O Usage | The value of network I/O that is consumed on the monitored machine/virtual machine. |
| Disk I/O Usage | The value of disk I/O that is consumed on the monitored machine/virtual machine. |
| JVM Performance |
JVM Heap Usage, JVM Memory Pools Settings, Garbage Collection performance, JVM System/Start-up Options, MBean metric values (for example, connection pool names and metric values, such as active connections, maximum connections, and so on) |