Discovery using behavior with tls_ssl_certs always uses "All" Discovery Functionality for ShazzamIssue Discovery using behavior with tls_ssl_certs always uses "All" Discovery Functionality for Shazzam. If the tls_ssl_certs is removed from "All" Discovery Functionality, even if the specified behavior has added tls_ssl_certs, it is unable to trigger certificate discovery from Shazzam. ReleaseSan DiegoCauseShazzam sensor is unable to fetch a valid behavior, as a result, it falls back to use the default 'All' functionality. In this case, because 'tls_ssl_certs' was removed from 'All', sensor skips certificate discovery. Steps to reproduce:- With certificate discovery enabled:1. Discovery Definitions > Functionality Definition > Open the record for "ALL"2. Remove "tls_ssl_certs" port probe from port probes, now default Shazzam will not trigger certificate discovery3. Create/use a behavior to add the "tls_ssl_certs" port probe4. Use the behavior to run Discovery, warning message pops up and Discovery is UNABLE to discover certificates from Shazzam Resolution Import the attached update set (PRB1542541_update_set.xml) and rerun Discovery. The import set should only contain changes to getBehavior method in Shazzam Sensor('discovery_sensor_0fe358250ab301500026926821fe5cac.xml')