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

add serial back to json output #102

Open
lukastribus opened this issue Jul 14, 2023 · 0 comments
Open

add serial back to json output #102

lukastribus opened this issue Jul 14, 2023 · 0 comments

Comments

@lukastribus
Copy link

Hello @job

in 38d058e some metadata outputs (Generated, Valid and Serial) were removed from rtrdump JSON output.

I think rtrdump should retain this functionality for machine based troubleshooting and monitoring purposes. The RTR serial number can otherwise only be extracted by running rtrdump in debug mode.

My use-case is that I'm monitoring serial increase over time with rtrdump and alert when there is a hung rtr server: https://github.com/lukastribus/rtrcheck/blob/d072488ab9e0f9bf9afe16f62dcd5c07a311ac1e/rtrcheck#L101

Tracked in lukastribus/rtrcheck#1

I realize there is rtrmon but it's use case seem to be quite different:

  • checkrtr is a shell script that can be dropped into any monitoring systems compatible with nagios plugins and will provide monitoring for availability and hung/stuck rtr server. It requires the user to know how to access the RTR endpoint and a sufficiently large check interval, but doesn't require any other inputs from the user.

  • rtrmon collects data from RTR endpoints, compares the data and provides the data for external consumption. It does not make it's own decision about whether a situation is good or bad, that is out of scope.

I don't see a lot of drawbacks to keep the rtr serial in the metadata json output of rtrdump.

Thank you,
Lukas

@lukastribus lukastribus changed the title rtrdump cleanup add serial back to json output Feb 22, 2024
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