- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2024 08:45 AM
Hi all,
We are trying to capture data regarding where a cloud hosted server is hosted. Currently we only have two options (On Prem and Azure). I don't see any OOB fields for this data.
Does anyone have any solutions regarding best practices for capturing this data? My idea was just to create a drop down with out two current options, and then populate that data as needed, but I wanted to make sure there wasn't something out of box I was missing.
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2024 01:39 PM
There are a couple of quick options I can think of, depending on the maturity of your organization.
The first, and the one that I would say is the MOST correct, is to create a datacenter CI, and relate the servers to the data center. The downside to this is the need to use CMDB Query Builder to produce a dataset that can easily be consumed by others (via reports, dashboards, etc.).
The second, and one I've seen used elsewhere (but don't really like), is to use the 'Location' field on the CI. The 'rightness' of this solution is questionable, but for a less mature organization is acceptable in my mind, since it is the location of the CI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2024 01:39 PM
There are a couple of quick options I can think of, depending on the maturity of your organization.
The first, and the one that I would say is the MOST correct, is to create a datacenter CI, and relate the servers to the data center. The downside to this is the need to use CMDB Query Builder to produce a dataset that can easily be consumed by others (via reports, dashboards, etc.).
The second, and one I've seen used elsewhere (but don't really like), is to use the 'Location' field on the CI. The 'rightness' of this solution is questionable, but for a less mature organization is acceptable in my mind, since it is the location of the CI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2024 08:29 AM
Thanks SteveMacWWT!
Yeah location is one of the options we've discussed, good to know others have done it as well. The datacenter CI is also a great idea, thanks for that! I don't think we're quite at that maturity level and I believe the main goal from the sys admin team is to have a way to quickly identify CIs in azure from a list view.
That being said, I can see this growing into using that as a solution as our processes mature. I'll mention it to the committee.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2024 08:20 AM
Hi @Derek C ,
I am not sure what i am mising in your question but I am not getting it.
On-Prem discovery allows to store the data in All Principal CMDB classes like Linux, Windows, Network etc apart from that Azure (Cloud), data will be updated in cloud specific table basically.
Based on CI type custom field you can managed CI belongs to Cloud or On-prem.
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thanks
AJ
Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/
ServiceNow Community Rising Star 2024
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2024 08:35 AM
Thanks for the reply Ajay! I did not realize there are separate tables for Azure devices. We are currently discovering Azure devices via the ACC Agent, but do have the ability to use the traditional IP range discovery as if it were on prem.
Do you have any more info on where I can find the best practices for discovering Azure CIs as the system is meant to discover them? I did see a ServiceNow Azure Service Graph Connector, but that didn't seem to be the data we're looking for based on the documentation I founds, but maybe I'm misunderstanding it.
Thanks,
- Derek
