Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose event processor status in metrics #409

Open
hakvroot opened this issue Nov 19, 2021 · 0 comments
Open

Expose event processor status in metrics #409

hakvroot opened this issue Nov 19, 2021 · 0 comments

Comments

@hakvroot
Copy link

hakvroot commented Nov 19, 2021

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 :

# per segment
axon_eventProcessor_segment_position{context=<>, component=<>, tokenStoreIdentifier=<>, processorName=<>, clientId=<>, segmentId=<>}=<position>
axon_eventProcessor_segment_onePartOf{context=<>, component=<>, tokenStoreIdentifier=<>, processorName=<>, clientId=<>, segmentId=<>}=<onePartOf>
axon_eventProcessor_segment_replaying{context=<>, component=<>, tokenStoreIdentifier=<>, processorName=<>, clientId=<>, segmentId=<>}=<0
1>
axon_eventProcessor_segment_caughtUp{context=<>, component=<>, tokenStoreIdentifier=<>, processorName=<>, clientId=<>, segmentId=<>}=<0
1>

# per processor
axon_eventProcessor_activeThreads{context=<>, component=<>, tokenStoreIdentifier=<>, processorName=<>}=<activeThreads>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant