02-20-2024 03:37 AM - edited 02-20-2024 05:29 AM
Hello all!
We have logging enabled and created an applet for a heartbeat message on a few switches. We did configure on every switch
service timestamps log datetime localtime msec show-timezone year
For Nexus everything is ok, but for the Catalysts I am getting 2 different timestamps, one for the applet (no right) and one for other messages(correct).
The timestamp from the event manager history is correct, but I don't know where the log message gets it's timestamp
Output for the same heartbeat message
#show log
Feb 20 11:17:16.454: %syslog-6-LOG: Syslog_Heartbeat: Hearbeat message on syslog.info
#show event manager history events
10 14395 Actv success Tue Feb20 12:17:16 2024 timer watchdog
Can I change this so i don't get funny looking messages like
<46>2024-02-20T12:17:17.461620+01:00 <source> 64265: Feb 20 11:17:16.454: %syslog-6-LOG: Syslog_Heartbeat: Hearbeat message on syslog.info
All other messages besides heartbeat have correct timestamp in the payload
<45>2024-02-20T12:18:54.600464+01:00 <source> 64266: Feb 20 2024 12:18:53.598 CET: %SEC_LOGIN-5-LOGIN_SUCCESS:
Thank you!
02-20-2024 05:44 AM
action x.x cli command "$_info-routername-config_$_event_pub_sec" <<- check this action
MHM
02-20-2024 09:52 AM - edited 02-20-2024 09:54 AM
Hi,
Thank you but unfortunately it doesn't work. I get the following error and the next action is not executed.
%HA_EM-3-FMPD_UNKNOWN_ENV: fh_parse_var: could not find environment variable: _info_routername
When i try to list all env variables form event manager, I get nothing in return.
I even tried "action x cli command "$_event_pub_sec"" , it does nothing but at least the next action is executed and a send a heartbeat log message to the server.
If it helps I run event manager version 1.0 and I don't think I can update.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide