This procedure is unsupported.
Articles in the "Unsupported Community Documents" space are not supported by ITRS support.
This article was written for version 7.0 of op5 Monitor, it could work on both lower and higher version if nothing else is stated.
When creating a filter for log monitoring it can sometimes be useful to test these by sending your own log messages.
In this short how-to we will use the command line utility logger (not to be confused with the Logger feature in op5 Monitor), to create our own syslog messages and send them to our op5 Monitor server.
Shell access to a Linux system
Remote logging configured - read this manual page for more information
The logger command line utility
A typical logger command looks something like this:
$ logger -i -t "service_abc" -p "daemon.warning" "Memory allocation failed"
The -i argument includes the process ID in the message, -t sets the ident and -p sets the syslog priority based on the provided facility and severity levels.
When the command above is executed it should result in something like this in the "Log messages" view: