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

devmon needs better output format #98

Open
lukehutch opened this issue Nov 22, 2020 · 0 comments
Open

devmon needs better output format #98

lukehutch opened this issue Nov 22, 2020 · 0 comments

Comments

@lukehutch
Copy link

devmon output is hard to parse in a future-proof way, because there is no record end marker, so a parser has to be stateful, and keep parsing drive metadata fields until it has all the fields it is expecting (then it can ignore everything else). Finding the last field the parser expects has to be used for the record end marker. But if field names change, this means that a devmon parser can break too.

Can you please support some other output format, enabled with a switch, e.g. JSON or XML, so that every change event can be parsed computationally in a more robust way? You can output one change event per line, and each line should be a complete JSON or XML document describing the change, and all the drive metadata after the change.

Thanks!

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