I have been playing with the embedded event manager and embedded syslog manager. I want to use an EEM script to detect an abnormal condition, then generate a syslog message about it. I want to then use an embedded syslog manager script to catch that syslog message, and route it to a specific host (by setting the stream number for that message to the correct one for a corresponding "logging host <host> filtered stream <stream>" command).
However, messages sent via the action_syslog TCL command in EEM scripts do not seem to get routed through ESM filters. My ESM filter sees system-generated syslog messages, and I see my EEM-generated messages correctly at my remote host if I don't use the "filtered stream <stream>" options to the logging host command, but I can't make them work together. Can ESM TCL scripts act on the output of EEM TCL scripts with action_syslog actions?
Alternately, is there another way to generate a UDP packet with (nearly) user-defined content via an EEM TCL script? (I am using syslog because its UDP based, and TCL can only do TCP. I want to send notification of an abnormal condition via UDP, and syslog is the only way I can see to do it from EEM.)