event syslog pattern --config changed

%PARSER-5-CFGLOG_LOGGEDCMD (x1): User:[chars] logged command:[chars]  This shows that parser is definitely not a valid pattern.

Explanation: The config logger, which logs every CLI command, has an option to
log messages to  syslog. Whenever a CLI command is executed, this message is printed.

Recommended Action: This message DOES NOT denote any error condition. It is a
part of the normal  operation of the parser and config logger. If you do not wish
to see this syslog message, type "no  cfglog send to syslog".


%SYS-5-CONFIG_I (x1): Configured from [chars] by [chars] ---- When I paste the full syslog message into Cisco tool, this what he takes out of it & explains it to you. As such I believe it should be the used pattern.

Explanation: The router configuration has been changed.

Recommended Action: This is a notification message only. No action is required.


The logging console command includes all the TTY lines in the device, not only the console TTY. For example, if you are running the debug ip rip command from a Telnet session to a VTY TTY on a router and you configure no logging console, the debugging messages will not appear in your Telnet command-line interface (CLI) session.

Specifying a level causes messages at that level and numerically lower levels to be sent to the console (TTY lines).


The logging count command counts every syslog message and time-stamps the occurrence of each message.

To enable system message logging to the terminal lines (monitor connections), use the logging monitorcommand in global configuration mode. 

To enable logging of system messages, use the logging on command in global configuration mode. This command sends debug or error messages to a logging process, which logs messages to designated locations asynchronously to the processes that generated the messages. To disable the logging process, use the no form of this command.