Apama 10.7.2 | Connecting Apama Applications to External Components | Standard Connectivity Plug-ins | The HTTP Server Transport Connectivity Plug-in | Monitoring status for the HTTP server
 
Monitoring status for the HTTP server
The HTTP server component provides status values via the user status mechanism. It provides the following metrics (where prefix is the name of the dynamic chain manager, typically HTTPServerManager):
Key
Description
prefix.status
Moves from STARTING to ONLINE when hostReady is called.
prefix.eventsTowardsHost
Number of requests resulting in events being sent to the correlator. This is the primary KPI for this component.
prefix.failedRequests
Number of non-2xx responses sent to clients, including errors generated from EPL. This is expected to be 0 and is a KPI with a warning threshold at 1.
prefix.staticFileRequests
Number of static files served to clients. This is a KPI.
prefix.authenticationFailures
Number of requests with invalid credentials. This KPI is not shown in Command Central by default. It has a warning threshold at 1.
prefix.numChains
Number of active chains for connections into this HTTP server instance. The chains can be reused between connections, but a single connection only uses one chain. This is expected to be between 0 and the maximum number of simultaneous connections which can be handled (see also maxConnections in Configuring the HTTP server transport).
prefix.requestSizeEWMAShortBytes
A quickly-evolving exponentially-weighted moving average of request sizes, in bytes.
prefix.requestSizeEWMALongBytes
A longer-term exponentially-weighted moving average of request sizes, in bytes.
prefix.requestSizeMaxInLastHourBytes
The maximum request size in bytes since the start of the last 1 hour measurement period.
prefix.responseSizeEWMAShortBytes
A quickly-evolving exponentially-weighted moving average of response sizes, in bytes.
prefix.responseSizeEWMALongBytes
A longer-term exponentially-weighted moving average of response sizes, in bytes.
prefix.responseSizeMaxInLastHourBytes
The maximum response size in bytes since the start of the last 1 hour measurement period.
For each request/response that is processed, the above MaxInLastHour values are updated if either of the following conditions is true:
*The size of the current message is greater than the existing maximum.
*The existing maximum value was set more than 1 hour ago.
Automatic responses are not included in the response size metrics.
Error responses are not included in the response size metrics. The request size metrics are calculated before compression and the response size metrics are calculated after decompression.
For more information about monitor status information published by the correlator, see Managing and Monitoring over REST and Watching correlator runtime status.
When using Software AG Command Central to manage your correlator, see also Monitoring the KPIs for EPL applications and connectivity plug-ins.