Couldn't figure out how to solve the error that followed after the execution of Discovery

[KotaY]

Hello folks, 

Hope you are doing very well!

Executing Discovery on our client production environment, it ended up with the following error log:

"Sensor error when processing HTTP - Classify: No sensors defined"

We have looked into how we could solve this issue, and yet we could not figure it out. 
Would you please show us how you would tackle this?

Many thanks,
Kota

[Selva Arun]

Hi,

Did you follow the solution provided in the article below?
Discovery - Evaluating the no sensors defined message - Support and Troubleshooting (servicenow.com)

Fixing the no sensors defined error message

To fix the No Sensors Defined error:

1. Navigate to Discovery Definition > Probes.
2. Search for the name of the probe. In this example, search for the name Shazzam.
3. Click the link in the Name field to go to the Shazzam probe page.
4. View the Sensors that react to this probe related list.
5. If a sensor exists in this related list, check that the sensor is active. If this column contains false, double-click the value and choose true from the drop-down menu to make the sensor active.
6. If a sensor does not exist in this related list, you can add a sensor. Click the Edit button.
7. The Edit Members page displays.

1. Search for the appropriate sensor from the Collection bucket.
2. Select the sensor, and click Add to add the sensor to the Sensors that react to this probe List bucket.
3. Click Save.
4. Verify that the sensor now appears and is active on the Sensors that react to this probe related list.

If you can not find a sensor that matches the probe in the Collection bucket, you must create a new sensor.

If you believe the solution provided has adequately addressed your query, could you please **mark it as 'Helpful'** and **'Accept it as a Solution'**? This will help other community members who might have the same question find the answer more easily.

Thank you for your consideration.

Selva