Managing Applications › Manage User-Defined Applications › Create a Web Application › Web Application Considerations

Web Application Considerations

When creating a Web application, keep in mind the following:

• You must use the Packets feed, a CA Standard Monitor, to monitor a Web application. The CA Standard Monitor is the only monitoring device that monitors a Web application. After you create a Web application, verify the Packets monitor feed is assigned to each server that belongs to the Web application.
• Do not create a Web application to monitor all HTTP traffic on a server. If you want to monitor all TCP-80 or 8080 traffic on a server, create a Standard application. A Web application is a monitoring device-intensive process because the monitor must process the HTTP header.
• Do not monitor Web applications on more than two non-standard ports. A non-standard port is a port other than TCP-80 or TCP-8080. For example, you can monitor Web applications on TCP-80 and TCP-8080, and two other ports. The additional resources that are required to process non-standard ports can negatively impact management console performance.
• When a user accesses a Web application through a proxy server, the management console reports the application traffic from the proxy server’s client network.

  If the proxy server uses X-Forwarded-For (XFF), the management console can translate the XFF header to report on the actual client network rather than the proxy server’s client network.

• The management console does not report HTTP sessions from any Web applications.
• The management console cannot monitor Web application traffic on HTTPS (TCP-443) because the URLs are encrypted. All such traffic shows up in the "Other" application.

More information:

Edit a Server

Support for XFF Translation