This program monitors the activity of the ePages Request Routers and Application Servers.
The server monitor is a CGI application, therefore it requires a web server. The program is installed in the directory $EPAGES_SHARED/Monitor.
Installation on Linux
Environment variable APACHE_MONITOR_ALLOW in /etc/apache2-epages/envvars defines what hosts can access the server monitor. Value is a space-separated list of hostnames/IPs. After changing ACHE_MONITOR_ALLOW the web server must be restarted (reload is not sufficient).
To run the monitor server, point your web browser to:
http://<your web server>/Monitor/spy.pl
Page: Cache Statistics
- Pool
-
application server pool
- ServerIP:Port
-
application server IP address and port number
- PID
-
application server process id
- Prio
-
application server priority (default=0)
- Status
-
application server status
- idle
-
application server is ready to process requests
- down
-
application server is not connected to the request router
- assigned
-
application server has been assigned to a request, but is not yet processing it
- working
-
application server is processing a request
- monitor
-
application server is processing a length request, such as export or import. The processing time will not be included in performance statistics.
- LastContact
-
seconds since the last request or heartbeat
- CacheItemCount
-
number of pending cache items
- CacheItems
-
actual cache item data
Page: Server
- Pool
-
name of the application server pool
- ServerIP:Port
-
application server IP address and port number
- PID
-
application server process id
- Prio
-
application server priority (default=0)
- Status
-
application server status (see above)
- LastContact
-
seconds since the last request or heartbeat
- Hits
-
number of requests that have been processed so far
- LongReq
-
number of requests with a processing time of more than 5 seconds
- MeanReq
-
number of requests with a processing time of less than 5 seconds and also excluding requests that are marked as monitor
- MeanTime
-
average processing time per request in milliseconds (counting only requests that fall into the MeanReq category)
- IdleTime
-
idle time since since processing the last request or startup
- Store
-
store name of the most recently processed request
- Site
-
GUID of the site (e.g. shop) of the most recently processed request
- ClientIP
-
client IP address
- Ext
-
script name extension of the most recently processed request
- URL
-
URL of the most recently processed request
Page: Pools
- Name
-
name of the application server pool
- CountServer
-
number of application servers
- Idle
-
number of application servers in state idle
- Assigned
-
number of application servers in state assigned
- Working
-
number of application servers in state working
- Monitor
-
number of application servers in state monitor
- Down
-
number of application servers in state down
- Hits
-
total number of sucessfully routed request
- UniqueMisses
-
number of request that were delayed, because all application servers were already in use, multiple tries of the same request where count at one
- Misses
-
number of request that were delayed, because all application servers were already in use
- Timeouts
-
number of requests running in time out (heavy traffic)
The following columns provide statistics about which strategy was uses to assign application servers to requests:
- ClientIP
-
application server was assigned based on the IP address of the client
- Site
-
application server was assigned based on the URL of the shop
- LastUse
-
the application server with maximum idle time was used
The following columns provide statistics about rejected requests:
- LimitExt
-
too many concurrent request for a script name extension
- LimitSite
-
too many concurrent request for a site by pool-wide limit
- LimitSpecial
-
too many concurrent request for a site with an individual limit
- LimitClient
-
too many concurrent request from the same client ip address
Page: Request Routers
- ServerIP:Port
-
request router IP address and port number (Message Center) Status - request router status:
- new
-
request router was just started, no message has been sent yet
- down
-
last message was sent successfully
- up
-
last message exchange failed
- Last Ping
-
seconds since the last successful message exchange