Discovery overwrote

[GP001]

Hi,

Discovery overwrote the old retired CI of the same name in August 2023 instead of finding the newer entry that was created in June. Can anyone please suggest what should i check here. Thank you.

[Harish Bainsla · Accepted solution]

Hi

Here are a few suggestions on what you can check to troubleshoot and address this issue:

1. Discovery Logs: Check the logs generated during the Discovery process in August 2023. Look for any errors or warnings that might indicate why the newer entry wasn't detected or updated. Pay attention to any messages related to duplicate entries or naming conflicts.

2. Discovery Configuration: Review the configuration settings for your Discovery tool. Ensure that it's configured to identify and update CIs based on unique identifiers, such as a CI's unique ID or a combination of attributes. If the configuration is not set up correctly, it might lead to overwriting instead of updating.

3. CI Naming Conventions: Verify that your CI naming conventions are consistent and unique. If there are inconsistencies or duplicates in naming, it could lead to confusion during the Discovery process. The tool may not correctly associate the older and newer entries if naming conventions are not followed.

4. CI Relationships: Check if the Discovery tool is configured to consider relationships between CIs. If the newer entry created in June has dependencies or relationships with other CIs, it might help the tool recognize and update it correctly.

5. Data Source Validity: Ensure that the data source providing information about the CIs is valid and up-to-date. If the source data is incorrect or outdated, it can lead to discrepancies in the Discovery process.

6. Custom Identification Rules: If your Discovery tool supports custom identification rules, check if there are any rules in place that might have contributed to the issue. Adjust the rules if necessary to improve the accuracy of CI identification.

7. Manual Verification: Manually verify the CI entries in your configuration management database (CMDB). Compare the details of the overwritten CI with the newer entry to identify any discrepancies. This manual review can help you understand why the Discovery process failed to recognize the correct version.

[Harish Bainsla · Accepted solution]

Hi

Here are a few suggestions on what you can check to troubleshoot and address this issue:

1. Discovery Logs: Check the logs generated during the Discovery process in August 2023. Look for any errors or warnings that might indicate why the newer entry wasn't detected or updated. Pay attention to any messages related to duplicate entries or naming conflicts.

2. Discovery Configuration: Review the configuration settings for your Discovery tool. Ensure that it's configured to identify and update CIs based on unique identifiers, such as a CI's unique ID or a combination of attributes. If the configuration is not set up correctly, it might lead to overwriting instead of updating.

3. CI Naming Conventions: Verify that your CI naming conventions are consistent and unique. If there are inconsistencies or duplicates in naming, it could lead to confusion during the Discovery process. The tool may not correctly associate the older and newer entries if naming conventions are not followed.

4. CI Relationships: Check if the Discovery tool is configured to consider relationships between CIs. If the newer entry created in June has dependencies or relationships with other CIs, it might help the tool recognize and update it correctly.

5. Data Source Validity: Ensure that the data source providing information about the CIs is valid and up-to-date. If the source data is incorrect or outdated, it can lead to discrepancies in the Discovery process.

6. Custom Identification Rules: If your Discovery tool supports custom identification rules, check if there are any rules in place that might have contributed to the issue. Adjust the rules if necessary to improve the accuracy of CI identification.

7. Manual Verification: Manually verify the CI entries in your configuration management database (CMDB). Compare the details of the overwritten CI with the newer entry to identify any discrepancies. This manual review can help you understand why the Discovery process failed to recognize the correct version.

[Sohail Khilji · Accepted solution]

@GP001,

Discovery will over write the existing CIs instead of creating a new CIs, if it find an old CI based on the CI identification peramters it will update the old CI. You got to check the Identification / reconcelliation perameters defined for the CI class which got updated.

it can be attributes like name, serialnumber etc...

As per your above query '' its seems like you have 2 CI with same name perameters'' old one and new one...

i hope this helps...

[GP001]

Thank you guys for your valuable response.!