rnetzel

Comments

  • I cant believe no one has run into this problem and found a solution. i guess they are mute.
    in Monitoring non default event logs Comment by rnetzel June 2017
  • yes i tried that already........"i copied the template Windows Event Log Monitor". its probably something to do with how i reference the log name but i need someone to confirm what is needed.
    in Monitoring non default event logs Comment by rnetzel June 2017
  • LOL thanks. also change the "NUMBER OF PAST POLLING INTERVALS TO SEARCH FOR EVENTS:" to something better when finalizing for production use. Overall the value of 1.5 should be good regardless of the polling interval (1 minute, 5 minutes, etc). with 1.5 it will always capture everything since the last Poll.
    in Monitoring non default event logs Comment by rnetzel September 2017
  • Nothing?! come on guys. someone out there knows how to get this working.
    in Monitoring non default event logs Comment by rnetzel June 2017
  • i think i finally got it to work! really dumb but you have to change the "Fetch Method" from WMI to RPC. i have my Custom log location set to.... Microsoft-Windows-Hyper-V-VMMS-Admin i also set "NUMBER OF PAST POLLING INTERVALS TO SEARCH FOR EVENTS:" to 100 so it would find an Error event. i found this in a SW…
    in Monitoring non default event logs Comment by rnetzel August 2017
  • great no response! i have a few logs i need to monitor also as Orion doesn't track Hyper-V deep enough. Logs i need to monitor for errors are.... Microsoft-Windows-Hyper-V-VMMS/Admin Microsoft-Windows-Hyper-V-VMMS/Storage Microsoft-Windows-Hyper-V-High-Availability/Admin i copied the template "Windows Event Log Monitor"…
    in Monitoring non default event logs Comment by rnetzel June 2017
Avatar