Validating Pure Storage FlashArray Data Using Pattern Debug<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This article explains how to validate the information returned by a Pure Storage FlashArray during ServiceNow Discovery. When troubleshooting data differences in the CMDB, it is important to confirm that the values retrieved by Discovery match the information provided directly by the FlashArray device. The steps below describe how to use Pattern Debug to view the exact API responses and ensure that the Discovery process is working as expected. Overview When ServiceNow discovers a Pure Storage FlashArray, it does so by using a series of API calls sent from the MID Server to the device. The responses from these API calls are then used to populate the storage server and storage volume records in the CMDB. If the information in the CMDB does not match what the customer expects, the first step is to verify what the device actually returned. Pattern Debug allows you to review the raw responses before ServiceNow processes them. Step One Identify the Pure Storage FlashArray that you want to troubleshoot. Confirm you can reach the device and that valid credentials are configured for Discovery. Step Two Open the Pure Storage FlashArray Discovery pattern in your instance. This pattern controls how ServiceNow collects data from the FlashArray. Step Three Start a Pattern Debug session for the target FlashArray. Provide the target address and select the appropriate MID Server. Begin the debug session so that you can run each step of the pattern manually. Step Four Run the early steps in the pattern that collect information about the storage array. Review the raw API response shown in Pattern Debug. This information is used to populate the storage server record in the CMDB. Step Five Run the steps later in the pattern that collect information about the storage volumes. Again, review the API response and note the values returned. These values are used to create or update the storage volume records in the CMDB. Step Six Run the steps that connect the storage server record with its related storage volume records. Confirm that the identifiers used to create these relationships match the identifiers returned by the FlashArray. Step Seven Compare the values shown in the Pattern Debug responses with the values stored in the corresponding CMDB records. If the values match the device responses, then Discovery is working as designed. If a value does not appear in the device’s API response, ServiceNow will not be able to populate it in the CMDB. Step Eight Check the identification rules for the storage server and storage volume record types in the CMDB. These rules determine how ServiceNow matches incoming data with existing records. If the FlashArray does not return a required identifier in the API response, matching may not perform as expected. Conclusion By reviewing the raw API responses through Pattern Debug and comparing them with the resulting CMDB records, customers can confirm whether ServiceNow Discovery is operating correctly or whether the FlashArray device is returning incomplete or unexpected information. This method is the most accurate way to validate data and understand how the resulting CMDB records are created.