<h2>Saving Pre Sensor and Post Sensor Processing time for Horizontal Discovery of Patterns</h2><br/><div style="overflow-x:auto"><p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"><strong><span style="font-size: 14.0pt;">Saving Pre Sensor and Post Sensor Processing time for Horizontal Discovery of Patterns</span></strong></p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"><strong>What is the problem?</strong></p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;">Earlier the metric for pre sensor processing and post sensor processing for horizontal discovery were not getting captured in the concerned discovery performance metric table (discovery_perf_metric_probe_sensor).</p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"><strong>What are we doing?</strong></p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;">Once the user triggers horizontal discovery and if the pattern going to be triggered has pre sensor(s) or post sensors(s) configured with them, then total time take to run the pre sensor or post sensors will be saved in the discovery performance metrics table. Time taken to run individual pre sensor or post sensor will be logged in node logs.</p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"><strong>What does it look like?</strong></p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;">discovery_perf_metric_probe_sensor table before the changes</p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"><img src="/sys_attachment.do?sys_id=83ee58d347fe611030fba325126d43a6" width="451" height="212" /></p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;">discovery_perf_metric_probe_sensor table after the changes. If the new attributes are not visible in the list view, then click on the gear icon the top right core and choose the Pre Sensor-Processing Time and Post Sensor-Processing Time attributes.</p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"><img src="/sys_attachment.do?sys_id=cbeed8d347fe611030fba325126d4309" width="452" height="212" /></p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;">Node logs after the change with the relevant filter.</p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"><img src="/sys_attachment.do?sys_id=57eed8d347fe611030fba325126d432e" width="452" height="166" /></p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;"> </p> <p style="margin: 0cm; font-size: 12pt; font-family: Calibri, sans-serif;">Note: The changes are present in the Vancouver release and June ’23 Store release of Visibility Content Plugin.</p></div>