Delayed Event Log Events

Crocker
A model citizen

Delayed Event Log Events

I've noticed over the past couple of days, when looking at the Event Log for some of our MX's, that there is a large delay in events appearing in the log. As an example, I'm looking at a network right now (local time 11:48AM CST) whose last event log entry was 8:30:31 AM; I know there's been plenty of events since then.

 

Has anyone else noticed this?

8 Replies 8
Mloraditch
Head in the Cloud

There is generally a small lag, but I've not seen nor do I see at quick glance anything like that for me right now. Have you verified that the time zone of the network matches your PC? That would explain some discrepancy.

If it does match, do relevant logs for the missing time show up eventually? My only suggestions to resolve would be reboots followed by support. Perhaps a firmware update if you lagging there.

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
rhbirkelund
Kind of a big deal
Kind of a big deal

Have you configured the network to the correct timezone?

Looking at the eventlog, in the Time column, you can see the timezone, in a light grey color.

You could also go to Network-Wide -> Configure -> General, and verify what timezone has been configured for the network.

LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.
Crocker
A model citizen

Yep, time zone is configured correctly at the locations I've noticed this at. I'm in the same timezone as them, as well.

rhbirkelund
Kind of a big deal
Kind of a big deal

Is there by any chance an "Events Dropped" event?

This usually indicates that there's been a burst of the preceeding event.

LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.
BlakeRichardson
Kind of a big deal
Kind of a big deal

Events dropped are a pain, the whole point of logging is to capture whats happening. 

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
rhbirkelund
Kind of a big deal
Kind of a big deal

Oh, I agree.

LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.
RWelch
Head in the Cloud
Head in the Cloud

EventLogs.png

Are you sure you are on "security appliance?"  Are there any filters set that might need to be cleared?

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
DarrenOC
Kind of a big deal
Kind of a big deal

Syslog, syslog, syslog……

Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels