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.

Sign up for GitHub

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

Jump to bottom

stats api #32

Open

svalaskevicius opened this issue Mar 12, 2016 · 1 comment

Labels

idea

Owner

svalaskevicius commented Mar 12, 2016

time started / time running
total number of commands processed
total number of events received from db
total number of events actually consumed by projections
mvg avg of commands per 1m / 5m / 15m
mvg averages of events received from db
mvg averages of events actually consumed by projections
projection state - have they caught up yet with db events? (per projection)
moving average of command retry if optimistic concurrency check fails
total number of command retry on occ
Number of failed commands due to occ
Number of failed commands due to logic
Number of ok commands
mvg avg number of events processed to catch up aggregates before each command

svalaskevicius added the idea label

Owner Author

svalaskevicius commented Mar 28, 2016

based on this, add a test for snapshotting - snapshotted aggregate should read less events from db on consecutive actions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment