Table used to store VM for Azure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2023 09:26 AM
Previously Azure VM record were stored in the cmdb_ci_azure_vm table. Most recently online documentation from serviceNow show that the Virtual Server (cmdb_ci_vm_instance) table is used.
Anyone knows the reason why the change? Is it based on the ServiceNow Cloud Management Platform having 2 versions - CMPv1 and CMPv2
Maybe a ServiceNow employee can respond on that
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2023 12:12 PM
hello bigfissy,
in my company, whe had take the decision to keep "out of the box" class, we are still using common class as cmdb_ci_linux_server or cmdb_ci_win_server, and play with the model ID class to identify the provider, it is working find for us, we can report from cmdb_ci class and retrieved all relevents informations for our KPI,process and report.
maybe this new way cmdb_ci_vm_instance is more relevent, but my may is pretty good to identify on premise server between logical server on cloud, by playing with model_id,
VM instance VMWARE= model ID VMWARE
VM instance AZURE= model ID AZURE Instance
VM instance AWAS= model ID AWS EC2
....
it is easier to report when you are managing onpremise and on cloud instance
hope can help;)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2023 12:27 PM
Apparently, ServiceNow retired using those tables per cloud provider. The table was used prior to migrating from CAPI-based cloud discovery to pattern-based discovery.