SolarWinds uses cookies on our websites to facilitate and improve your online experience. By continuing to use our website, you consent to our use of cookies. For further details on cookies, please see our cookies policy.
Hide this message
Webinar: A checklist for planning your Network Performance Monitor (NPM) upgrade
Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.
Register now.
Updated June 8, 2018
In most circumstances, File Existence Monitor can locate a file if the queried file is on the polling engine. However, the * wildcard may not work correctly and the queried file may not be found on a monitored node.
Ensure that the file path specification contains the variable for the IP address. When using this specification, you can use the * wildcard to check if the file exists.
For example, if you check the path D:\XLFRE_PRD\logs\java_pid4341.hprof , 4341 could be any number.
The correct file path specification to enter into the monitor would be:
\\${IP}\D$\XLFRE_PRD\logs\java_pid*.hprof
When you test the monitor to check if a file exists, make sure you are using the entire file name and the extension is NOT hidden from view in File Explorer.