Forum Discussion
yaquaholic
2 months agoContributor II
We've got similar issues, where we have hundreds of MSSQLSERVER instances.
We managed to resolve the problem using the API first searching /api/device/ for the MSSQLSERVER and then using /api/relationship look up the parents name adding it to the devices:
MSSQLSERVER (Virtual Machine Parent Name)
Then updating the device's name with the API.
Then searching for the databases and adding the parent name which then contains the root device's name:
<DB name>MSSQLSERVER (Virtual Machine Parent Name)
And again updating the device's name with the API.
And all to save our Service Desk 5 minutes logging onto SL1 and having a look 🤷
Related Content
- 5 months ago