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

SPIKE: Design doc for auditing tool for Waltz #23

Open
whynick1 opened this issue Jul 8, 2019 · 0 comments
Open

SPIKE: Design doc for auditing tool for Waltz #23

whynick1 opened this issue Jul 8, 2019 · 0 comments

Comments

@whynick1
Copy link
Contributor

whynick1 commented Jul 8, 2019

We will need an auditing tool for Waltz to validate that no transactions are ever lost. Ideally, this tool will run continuously, and immediately alert us to any lost transactions.

@ymatsuda, have you thought about any strategies for this? It seems loosely similar to some of the auditing work for Kafka.

I think that there are two things that need to be audited: 1) that a transaction wasn't lost before it was even persisted to Waltz (i.e. client thinks it was persisted, but it wasn't successfully), and 2) that a transaction was persisted to Waltz, but later disappeared for some reason.

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