Hi,
From an operational perspective, we want to have insight in the TrackingProcessor status.
We have an endpoint, which reports the status, and we can aggregate this information for all processors in a UI.
This is how the json looks like now [1]:
When AxonServer is in debug mode, it reports how far it is with serving the events. (I my interpretation is correct):
axonserver_1 | 2019-03-05 11:30:25.366 INFO 7 — [event-stream-40] i.a.a.l.EventStreamController : Start tracker from token: 1127686
axonserver_1 | 2019-03-05 11:30:25.405 INFO 7 — [event-stream-40] i.a.a.l.EventStreamController : Done processing backlog at: 1128186
Now I wonder, why the processor reports it is 'caughtUp, while events are still being served?
Could it be this only applies when ‘replaying’ events?
Regards, Christophe
MacBook-Pro:axon-props christophe$ http :8030/axon/processors/
HTTP/1.1 200
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
[
{
"name": “eu.blox.engine.asset.query”,
"status": [
{
"caughtUp": true,
"replaying": false,
"segmentId": 0,
"trackingToken": “IndexTrackingToken{globalIndex=1127617}”
}
]
},
{
"name": “eu.blox.engine.product.query”,
"status": [
{
"caughtUp": true,
"replaying": false,
"segmentId": 0,
"trackingToken": “IndexTrackingToken{globalIndex=1128032}”
}
]
},
{
"name": “eu.blox.engine.account.query”,
"status": [
{
"caughtUp": true,
"replaying": false,
"segmentId": 0,
"trackingToken": “IndexTrackingToken{globalIndex=1127416}”
}
]
}
]