...
Metric | Metric available? | Exposed via Prometheus endpoint? | Comment | |||||||
---|---|---|---|---|---|---|---|---|---|---|
Availability of policy-apex-pdp | Yes | Yes | Exposed by policy-apex-pdp healthcheck and policy-pap consolidated healthcheck. | |||||||
TOSCA Policy Deployment counter (per apex-pdp instance) policyDeployCount | Yes | Yes | Exposed by policy-pap statistics
| |||||||
TOSCA Policy Execution counter (per apex-pdp instance) # of policies executed | Yes | Yes | ||||||||
Engine stats (by engineID per apex-pdp instance) eventCount: number of APEX events processed | Yes | Yes | ||||||||
Count of events processed (per engine thread, per apex-pdp instance) # of incoming trigger events processed by policy-apex-pdp *Note: the stats currently displays APEX event counters processed by the engine | Yes | Yes | ||||||||
Latency | Yes | Yes | Time taken for processing an incoming APEX event *Note: the stats currently displays execution time for processing APEX policy, and is a measure of system saturation and is sufficient | |||||||
Kafka consumer lag | No | No | Can be implemented outside of the Policy FWK. Monitor kafka consumer lag increase for kafka/dmaap-message-router topics related to apex-pdp |
...