Pattern (Azure Virtual Machine) Issue

[SASIKUMARR]

We Implemented Azure Cloud discovery able to discover VM's from  cloud discovery schedules .

But for few schedules pattern will be failed showing Identification Engine: Discovery status is FAILURE, CI Type cmdb_ci_vm_instance cannot be created since there are no attributes defined. Debug pattern to understand why no attributes have been assigned.

Geting error in Exploring Ci

We have Object ID is the Identifier for the cmdb_ci_vm_instance, we are getting this attribute in ecc input payload.

Successful pattern for few cloud schedules

How can we slove this issue? Can you please give insights

#Discovery #ITOM

[Anmol8 · Accepted solution]

Hello,

The error you're encountering during Azure Cloud discovery, where the CI type `cmdb_ci_vm_instance` cannot be created due to missing attributes, typically indicates a problem with the identification and reconciliation process. Specifically, it suggests that the discovery process is receiving data, but it's failing to correctly map that data to the expected CMDB attributes for virtual machines.
Steps to Troubleshoot and Resolve:

1. Verify the Discovery Pattern Configuration:
- Check the Pattern: Go to the Discovery Patterns for Azure and ensure that the pattern associated with discovering `cmdb_ci_vm_instance` is correctly configured. The pattern should have all the necessary steps and scripts to extract the attributes from the payload.
- Debug the Pattern: Use the "Debug Pattern" feature to step through the pattern execution and see where it might be failing. Look at the specific step where the attributes should be populated.

2. Review the ECC Queue Payload:
- Inspect the ECC Input Payload: Since you mentioned that the Object ID (which is the identifier) is present in the ECC input payload, verify that all other required attributes for `cmdb_ci_vm_instance` are also present. Ensure that the data in the payload is correctly formatted and complete.
- Mapping to Attributes: Ensure that the payload data is being correctly mapped to the respective attributes in the CMDB. The identification rule should properly associate the incoming data with the existing CI or create a new one if needed.

3. Check Identification Rules:
- Identification Rule for cmdb_ci_vm_instance: Go to the "CI Identification" rules and locate the rule for `cmdb_ci_vm_instance`. Ensure that the Object ID (and any other unique attributes) is correctly set up as an identifier.
- Attribute Mapping: Ensure that the identification rule correctly maps the attributes from the discovery data to the CMDB attributes.

4. Investigate the Attribute Assignment Logic:
- Attribute Population: Ensure that the pattern or script logic correctly assigns values to the attributes before attempting to create or update the CI. If an attribute isn't being populated, it may prevent the CI from being created.
- Script Errors: If the pattern uses custom scripts, check those scripts for any errors or issues that might prevent attributes from being set.

5. Check CMDB Health and Integrity:
- CMDB Health Dashboard: Use the CMDB Health Dashboard to check for any issues with data quality or identification rules that might affect the creation of `cmdb_ci_vm_instance` CIs.
- CMDB Data Integrity: Ensure there are no conflicts or issues within the CMDB that could prevent the CI from being created.

6. Log Analysis:
- MID Server Logs: Check the MID server logs (agent logs) for any errors or warnings that occurred during the discovery process. These logs can provide more detailed information about where the failure occurred.
- Discovery Log: Look at the specific discovery log for the failed schedule to get a more detailed view of the failure. The log should provide information on why the attributes were not assigned.

7. Update ServiceNow:
- Patching and Upgrades: Ensure that your instance is up-to-date with the latest patches or updates. Sometimes, bugs in the discovery process are resolved in later releases.

If the Issue Persists:
- Contact ServiceNow Support: If the issue remains unresolved after following the above steps, it may be necessary to open a case with ServiceNow Support. Provide them with details of the discovery pattern, ECC input payload, and any logs or errors you've encountered.Summary:**
- Debug the discovery pattern to ensure it’s properly extracting and assigning attributes.
- Verify the identification rules for `cmdb_ci_vm_instance` to make sure they correctly map and identify CIs.
- Check the ECC input payload to ensure all required attributes are present and correctly formatted.
- Review logs and configuration for any issues or inconsistencies.

By methodically checking each aspect of the discovery process, you should be able to identify and resolve the issue, allowing the CIs to be created or updated correctly.

Thanks,

Anmol

[gauravbhandari0]

Hi Sasikumarr,

did you find any solution to this error? We are facing similar errors during Azure discovery. Are you able to solve it?

[Anmol8 · Accepted solution]

Hello,

The error you're encountering during Azure Cloud discovery, where the CI type `cmdb_ci_vm_instance` cannot be created due to missing attributes, typically indicates a problem with the identification and reconciliation process. Specifically, it suggests that the discovery process is receiving data, but it's failing to correctly map that data to the expected CMDB attributes for virtual machines.
Steps to Troubleshoot and Resolve:

1. Verify the Discovery Pattern Configuration:
- Check the Pattern: Go to the Discovery Patterns for Azure and ensure that the pattern associated with discovering `cmdb_ci_vm_instance` is correctly configured. The pattern should have all the necessary steps and scripts to extract the attributes from the payload.
- Debug the Pattern: Use the "Debug Pattern" feature to step through the pattern execution and see where it might be failing. Look at the specific step where the attributes should be populated.

2. Review the ECC Queue Payload:
- Inspect the ECC Input Payload: Since you mentioned that the Object ID (which is the identifier) is present in the ECC input payload, verify that all other required attributes for `cmdb_ci_vm_instance` are also present. Ensure that the data in the payload is correctly formatted and complete.
- Mapping to Attributes: Ensure that the payload data is being correctly mapped to the respective attributes in the CMDB. The identification rule should properly associate the incoming data with the existing CI or create a new one if needed.

3. Check Identification Rules:
- Identification Rule for cmdb_ci_vm_instance: Go to the "CI Identification" rules and locate the rule for `cmdb_ci_vm_instance`. Ensure that the Object ID (and any other unique attributes) is correctly set up as an identifier.
- Attribute Mapping: Ensure that the identification rule correctly maps the attributes from the discovery data to the CMDB attributes.

4. Investigate the Attribute Assignment Logic:
- Attribute Population: Ensure that the pattern or script logic correctly assigns values to the attributes before attempting to create or update the CI. If an attribute isn't being populated, it may prevent the CI from being created.
- Script Errors: If the pattern uses custom scripts, check those scripts for any errors or issues that might prevent attributes from being set.

5. Check CMDB Health and Integrity:
- CMDB Health Dashboard: Use the CMDB Health Dashboard to check for any issues with data quality or identification rules that might affect the creation of `cmdb_ci_vm_instance` CIs.
- CMDB Data Integrity: Ensure there are no conflicts or issues within the CMDB that could prevent the CI from being created.

6. Log Analysis:
- MID Server Logs: Check the MID server logs (agent logs) for any errors or warnings that occurred during the discovery process. These logs can provide more detailed information about where the failure occurred.
- Discovery Log: Look at the specific discovery log for the failed schedule to get a more detailed view of the failure. The log should provide information on why the attributes were not assigned.

7. Update ServiceNow:
- Patching and Upgrades: Ensure that your instance is up-to-date with the latest patches or updates. Sometimes, bugs in the discovery process are resolved in later releases.

If the Issue Persists:
- Contact ServiceNow Support: If the issue remains unresolved after following the above steps, it may be necessary to open a case with ServiceNow Support. Provide them with details of the discovery pattern, ECC input payload, and any logs or errors you've encountered.Summary:**
- Debug the discovery pattern to ensure it’s properly extracting and assigning attributes.
- Verify the identification rules for `cmdb_ci_vm_instance` to make sure they correctly map and identify CIs.
- Check the ECC input payload to ensure all required attributes are present and correctly formatted.
- Review logs and configuration for any issues or inconsistencies.

By methodically checking each aspect of the discovery process, you should be able to identify and resolve the issue, allowing the CIs to be created or updated correctly.

Thanks,

Anmol

[SK Chand Basha · Accepted solution]

Hi @gauravbhandari0

Can you check the versions of the pattern if its has customized please revert it to OOB pattern.