(1) Bind tasks, including expiration time Probe Group, decentralized monitoring, frequency, customized execution plan, check DNS, when Host disables ICMP, try to perform Ping operation in TCP mode, browser type, filter monitoring Probe by operating system/browser, select only monitoring Probe with specified client plug-in installed, bandwidth options, intelligent noise reduction; and other indicators are consistent; check whether these parameters of the tasks that need to be bound are consistent; (2) From the report, the above settings are consistent, and logically they should be able to be bound; (3) Check the parameter settings in the database and find that the parameter "reg_plugin_opt" settings are inconsistent. The main task database entry is "null", and the copied subtask is only "" (4) The settings are a client plug-in function
It is found that the main task was created in 22 years, and the copied task was created in 25 years. The settings are a new function after the creation of the main task. Therefore, the main task and the sub-task have different storage formats. Different storage formats of the corresponding task settings will also lead to unsuccessful binding;
When the front-end cannot see where settings are inconsistent, check thecorresponding settings through the interface parameters. If you directly check the parameters settings of the corresponding task, the amount of data is too large, and some will be interference items; In the binding module, select the tasks to be bound, view the interface, as shown in the figure, copy the obtained parameters, and put them in the text for comparison;