Why some patterns are not firing on Discovery for Cloud (Azure) ?

Cuneyt Bozok
Tera Guru

Hi, 

 

I'm testing the Azure Cloud Discovery, I have set everything from Azure data center, mid server, service account I try to discover a datacenter, but I can only see 8 patterns are actually working. But there are many patterns for Azure. I can get most of the resources by adding the resource type path to the "sa_cloud_inventory_resource_whitelist_list" table but some of them are not responding to that method for example the Priva DNS Zones. Adding "Microsoft.Network/privateDnsZones" to the list is not working, it has a dedicated pattern called "Azure Private DNS Zone (LP)" which is "active=false" by default. But when I activated it, just like others, it is not working. 

 

I tried debugging but I don't know the input parameters of the object id which is another question of mine. 

 

My questions are,

 

1- Why the rest f the patterns are not working? Should I do some additional ?configuration ?

2- Why some of the patterns are "active = false" by default. Such as Azure Private DNS Zone (LP)

3- I can't debug the Cloud Patterns without an "object id input", some of them are easy but some require multiple inputs. Do you have any idea how to debug them ?  

4- What does it mean "from execution" in debug screen? I thought it could be a previously executed discovery log where that pattern is triggered but It always shows "No executions found". For example, I can't use that method even with the 8 working patterns.

 

Sorry for my ignorance, I'm just trying to understand the basics of Cloud Discovery.

 

Thank you.

 

2 REPLIES 2

Randy Fisher
Tera Expert

Cuneyt,

 

Not sure if you ever got this resolved but I had a similar issue today when testing and I ran across your post.  We tested in our dev instance where all the patterns were active.  When I moved to prod, only some of the patterns were active and I am unsure why.  I marked them all as active, re-ran discovery, and, same as you, there was no improvement.  I had some other issues with dev and as I was troubleshooting, I had to re-create the discovery schedules sometimes to see any improvement.  So in prod, I then deleted my discovery schedules, re-created them, and the patterns all ran on the next discovery.  Hopefully you already had this figured out.  Best of luck!

Hi Randy,

 

I actually found that I should migrate the patterns. If haven't done it I suggest you do, it helped us to use all the azure patterns we needed.

 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0827153