What would you see in the Discovery pattern log that you would not see in the ECC Queue?

When executing pattern-based discovery in ServiceNow, the underlying pattern engine dictates a complex sequence of granular operations. The Pattern Log is a dedicated, debug-level viewer that displays the exact success, failure, execution duration, and intermediate variable outputs of each individual pattern step (such as Parse Variable or WMI query). Conversely, the External Communication Channel (ECC) Queue operates as an asynchronous communication matrix capturing raw data outputs. While the ECC queue reliably stores the aggregate XML or JSON payload encompassing the finalized CI attributes resulting from the pattern, it inherently lacks the internal, step-by-step diagnostic execution flow of the pattern engine itself, which is uniquely vital for troubleshooting pattern logic and classification failures.

B. Payload of CI attributes and relationships: This consolidated payload containing discovered components is exactly what the pattern engine compiles and outputs directly to the ECC Queue payload record.
C. Shazzam probe payload: Shazzam is an initial port-scanning probe whose raw XML output results and port responses are standardly returned directly to the ECC Queue input record.
D. Relationships created: Identified target CI relationships are serialized inside the final identification payload, which is explicitly logged within the ECC Queue input record prior to IRE processing.

ServiceNow Product Documentation: IT Operations Management > Discovery > Pattern Designer > View discovery pattern log (Section: Pattern log layout and individual step execution status).

ServiceNow Product Documentation: IT Operations Management > Discovery > Discovery administration > Discovery ECC Queue.