In case of missing script-file, we throw RuntimeException in getRuntimeAttributes which results in event with following description.
<p>A DeviceConfig-default outage was identified on interface
192.168.1.123 because of the following condition: Unexpected exception while polling PollableService[location=Default, interface=PollableInterface [PollableNode :192.168.1.123], svcName=DeviceConfig-default]. java.lang.RuntimeException: java.io.FileNotFoundException: Couldn't find file juniper-vsrx-default.dcb in etc/device-config folder.</p> <p>
A new Outage record has been created and service level
availability calculations will be impacted until this outage is
This is good to know the problem but once user fixes it, they can't do manual trigger since this fails early and doesn't go through monitor.
One way to fix this is pass on the error to monitor and monitor returns the failure. In this case, an actual entry gets created in the DeviceConfig table and UI will see the device.