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
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