Discovery Behavior not launching CI Classification

[Gus1]

I've setup a Discovery Behavior for HTTP, the Shazzam probe is being triggered and I can see it is indeed only checking the HTTP ports, the problem is now that the HTTP Classification probe does not get triggered. If I change the Discovery Schedule's MID Server Selection method from Behavior to Mid Server, select the Mid server and not use a behavior the HTTP Classification does run. We're wanting to explore using a Behavior to help improve discovery run times and avoid unnecessary classifications from running. Does anyone have any suggestions for this or see anything I might've configured incorrectly? The port does return open in the ecc queue.

Screenshot of the schedule

Screenshot of the Behavior

Screenshot of the Discovery Functionality

[Vasantharajan N]

@Gus1 - Did you check the discovery logs and ecc queue that help us to understand which phase of discovery is failing?

[Gus1]

Hi @Vasantharajan N, thank you for the reply.

I have checked the ecc queue and logs. This is a screen shot of the status that was created when I ran the discovery. You'll notice the discovery starts and then states completed. 

There are 2 ecc queue records that get created, an output for the shazzam probe and an input, the input as I understand it is the data that is returned from the output, here is a screen shot of the input: You'll notice the port for HTTP is open but the HTTP Classification probe is never triggered. Am I missing something in my behavior? 

[Gus1 · Accepted solution]

I figured this out. It turns out I overlooked a note in the Documentation here: https://docs.servicenow.com/bundle/vancouver-it-operations-management/page/product/discovery/task/cr...

This is the Note: Functionality criteria are required for Windows MID Servers only, and only when the behavior controls Discovery across multiple domains. When the instance launches the Shazzam probe for a Discovery in which a behavior defines multiple MID Servers to scan multiple domains, the functionality criteria determine which MID Server process the results of the probe.

I deleted the functionality criteria I had created since I technically don't need it and it started to work as expected. I can now run discovery specifically for HTTP without having to run it for the other protocols.