The Apache Agent automatically discovers incoming HTTP requests to Apache Web Server nodes as business transaction entry points. Splunk AppDynamics uses URI-based naming for transactions originating at Apache Agent nodes. The agent discovers exit points to Apache modules and resolves them to the downstream tier or backend. See Apache Web Server Backend Detection.

Business transaction naming is limited to URLs or the WEB type. This provides limited options for match and split rules.

The Apache Agent tracks the following metrics for web servers:

• Calls per minute and time spent in the web server tier
• Calls per minute and time spent in Apache module backends
• Number of errors

The agent identifies slow and stalled transactions according to dynamic baselines. When it detects an HTTP response code greater than 400, the agent identifies the transaction as an error transaction.

Transaction snapshots taken on Apache Web Server nodes include the following data:

• URL
• HTTP error codes
• HTTP request data:
  • Cookie, including JSESSIONID
  • Referer
  • X-Forwarded-For
  • SM_USER
• Exit calls to Apache modules