Debugging - Probe Post Processor Scripts & Navigating around mid server script includesMany a times one can come across a post process script which may be defined for a discovery probe for e.g. Linux - Network probe These post processing scripts in turn will make method calls to various script includes and re-use the existing methods defined in these script includes. On hovering over these script includes it will give you the option to navigate to the script include record but here one has to be very sure because most of the times it will be misleading. Since probe post processing scripts are meant to be executed on the mid server so hence they won't have access to script includes residing on the instance. Therefore we have mid server script includes(ecc_agent_script_include) defined which are executed at the mid level. The problem arises when we have the same script name for mid server script includes(ecc_agent_script_include) & instance script includes(sys_script_include). Due to which the default navigation suggestion from any post processor script will point to sys_script_include which will be misleading and lead to confusion. In such cases one should also check the ecc_agent_script_include table for such names. For our understanding I am In the Linux - Network probe the post processor probe var idutil = new IDSensorUtil(); Here on hovering over IDSensorUtil will have hyperlink suggestion to sys_script_include record which is wrong. This happen since we have 2 records with same name IDSensorUtil in both the tables ecc_agent_script_include & sys_script_include So In a nutshell a post processor script will always make a call to only mid server script includes(ecc_agent_script_include) and one should not be mislead by the hyperlink sugggestion.