-
Notifications
You must be signed in to change notification settings - Fork 52
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
backlog in reverse order #74
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When iterating over backlog, messages appear in reverse order. The most recent message is first (reading top down) and the first messages is last. For example, I have a condition that triggers when a network interface state changes. When the interface goes down, then back up the messages in the backlog will be ordered with the up message printed before the down message.
Custom Message:
Last messages accounting for this alert:
SW01 Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet33, changed state to up
SW01 Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet33, changed state to down
They should be printed in the order they are received:
down
up
The text was updated successfully, but these errors were encountered: