Cloud Discovery - discovering Availability Set and Availability Zone - (Kingston Version)

gowthamram
Kilo Contributor

‎03-24-2019 10:31 PM

Hi,
We have discovered AWS and Azure Resource types and respective items using Cloud Discovery. One of the CI Class used is Availability Zone in ServiceNow.
These items are discovered from Availability Zone (Resource Type Name in AWS) in AWS.
For Azure it is Availability Sets(Resource Type Name in Azure).
Above items are discovered under Availability Zone (CI Class in ServiceNow)in ServiceNow. But Properties of the Availability Sets (Azure) and Availability Zone(AWS) are different. So there should be different Classes used in ServiceNow for Azure and AWS Resource type instead in same CI Class(Availability Zone). Would like to know the alternate or better solution for the above.

Thanks in Advance!.....

Labels:
0 Helpfuls
  • 1,416 Views
2 REPLIES 2

Hardik Benani
Mega Sage
Mega Sage

‎03-25-2019 03:56 PM

Totally agree, I have raised this with support but it's not changing anytime soon. You can however modify the Cloud Response processor script to put it into different table. Below are the steps.

1. Navigate to table: sn_capi_resource_type 

2. Modify the below entry to new table name to new table.

find_real_file.png

 

3. Modify the entries in below table to point to new table and mappings. Ensure the mappings are correct and the CI fields exists. Ru-run the discovery. You can also skip step 1 and step 3 and map additional missing fields just here. You can check the response payload in the Cloud API Logs.

find_real_file.png

4. Please note if you are referencing the azure availability zones somewhere in your provisioning - you will also have to modify those filters.

Other preferred option is to just create a new Cloud API Interface Extension, New Discovery steps and new response processor. 

Hope this helps.

Preview file
63 KB
Preview file
223 KB

Amar_Be
Kilo Sage
In response to Hardik Benani

‎01-26-2025 11:10 PM

Hi,

 

I'm working with the Service Graph connector for Azure.

It is also putting the availability sets into the class availability zone , while an availability set class exist.

I'm in release Washington, is there a reason why ServiceNow is not using OOTB the correct class?

What is the  best way to redirect the CIs to the availability set class?

I would like to avoid customizing the OOTB transformation, is it possible to do the correction without customizing?

 

Thanks

0 Helpfuls