In this recipe, we explore the options available for troubleshooting and debugging event scripts. Because event scripts are, by their nature, triggered by network, or device-related events rather than human interaction, the ordinary interactive methods for troubleshooting software complexity and bugs are left wanting. In order to optimize the code/run/debug cycle for event scripts, we outline some useful techniques here to help.
Debugging event scripts
Getting ready
In order to complete this recipe, you should have access to the JUNOS router or device. You don't need an actual event script to debug. We'll just walk through the techniques with some examples.