You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To determine the overall health of AxonServer and the event processing applications there are quite a large number of metrics available. Unfortunately we find that one of the key indicators for health, the ability to process events, is not completely covered in the metrics. This gap pertains the insight into unclaimed segments and duplicate segment claims.
Currently this information is available (in the AxonServer UI) through the AxonServer REST API under /v1/components/<component>/processors?context=<context> which describes the state per event processor.
Proposed solution
Based on the API we propose adding the following metrics (gauges) to AxonServer :
Issue
To determine the overall health of AxonServer and the event processing applications there are quite a large number of metrics available. Unfortunately we find that one of the key indicators for health, the ability to process events, is not completely covered in the metrics. This gap pertains the insight into unclaimed segments and duplicate segment claims.
Currently this information is available (in the AxonServer UI) through the AxonServer REST API under
/v1/components/<component>/processors?context=<context>
which describes the state per event processor.Proposed solution
Based on the API we propose adding the following metrics (gauges) to AxonServer :
The text was updated successfully, but these errors were encountered: