I have successfully integrated ServiceNow using the WebAPI tile to grab Incidents, Change Tasks, and Problems for Microsoft Windows based computers.
I used the example from the Coffee Break video as follows:
This does not work for non Microsoft Windows computer objects.
Does anyone have a solution that works for Linux Computers, F5 devices, Application CIs or Databases? I have created the perspective and targeted the “Object” class in the Perspective Settings.
I’d ultimately like to be able to drill down to any of these SCOM objects (i.e. Linux Computer) and hit the Service Now perspective and get data from Service Now based on the object type under current scope. But, If it’s not a Microsoft Windows computer, I get “Object reference not set to an instance of an object”.
You can do this a number of ways.
Simply searching for the object and looking at the monitored entity perspective for an object is by far the easiest – This will show all of the properties of the object:
You can also use PowerShell.
First, we get the correct class:
get-scomclass -DisplayName *linux* | select displayname,name | sort displayname
Which tells us that we are after Microsoft.Linux.Computer
I only have a handful of Linux machines, so the next bit is easy:
get-scomclass -Name Microsoft.Linux.Computer | Get-SCOMClassInstance | fl *
It’s likely that either of these will suffice:
Either of these methods can be replicated to find the other objects properties.
If you prefer, you can also view the detail view of a state view in the SCOM console, selecting an object and looking there:
If you’ve set the tableName for the server/F5/App then have you tried just using the Name as it appears in Service Now?
For example, for our Mobile Iron email solution – I found it in the SN CMDB under Applications which gave me the Table in the browser address bar, I then just copied the Name field and used:
That might not be much use for Perspectives, but it’s handy for when you just have a handful of objects you need to add SN info for. I used the above for CMDB information so the Ops Team can see who to contact when something is broken.