SystemEdge Log File Monitor match traps generate "Error Processing Event 0x116002f" events on the Host_SystemEdge device model in Spectrum
Users that are using process models as resources in services, wanted to have log monitors to have the ability to affect the condition of a process model.
SystemEdge Log File Monitoring functionality requires users to configure a "Monitored Process Log File Mapping" which associates a log file to a process and then create a process monitor for that process in SPECTRUM.
If the Monitored Process Log File Mapping is not setup and the process is not being monitored in SPECTRUM, users will seeing the following events in SPECTRUM b/c we are trying to forward the log monitor event to a process model that doesn't exist.
Error processing event 0x116002f - Details: No device
hostname, IP address or mapped target (logfile) could be found. Provided
input string was: "Test " System Host_systemEDGE 0x3dc0000
When setting up Log File Monitors on a SystemEdge host, users are now required to "Monitored Process Log File Mapping" and map the log file to a process and setup a process monitor for that process.
1. From the Information tab expand the System Resources -> Monitored Logs and Process Logs:
2. Click on the "Add" button in the table.
3. Specify a "Log FIle Name" ie... C:\TEST.txt
4. Specify a Process Name. ie... notepad.exe
5. From the Information tab, expand the System Resources ->Running Monitored Processes -> RFC270 -> Monitored Process table.
6. Add a process monitor for the process associated with the log file "Monitored Process Log File Mapping" table.
The following two options can also be used.