Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Access to the object schema you’re importing the data to can be limited to a certain Jira group. However, members of the group jira-system-administrators can always modify the object schema settings. This schema can be restricted from members of the jira-administrators group.
No. As of factory default Apple iOS or Android do not support any kind of remote access like SSH or SNMP. We cannot recommend Jailbreaking or Rooting your devices to gain remote access.
Discovery will find the laptops connected to your network at the time of scanning. It will collect IP and MAC address without using credentials to get into the machines. But if you also provide credentials equivalent to local admins, you are able to get a lot more information from the machines like hostname, user profiles, CPU, RAM, installed software etc. (See Data collected by Assets Discovery)
As of the initial version of Assets Discovery, it will not consider any existing object types or objects in your Assets configuration. When you run the first import, you will need to select which object schema to import to and Assets Discovery will build up an object type structure there with all the discovered data. This topic is something we will look deeper into though.
Assets Discovery supports SNMP version 1, 2, and 3.
Yes. Since Release 2.2.0 the Discovery Tool will run on a Linux Desktop Environment with Mono installed. Take a look to at the Documentation Page for it.
Please, make sure that the user that is running the JIRA Instance (Tomcat-Service) has read and write permissions at the configured import folder and files.
This depend on many various factors in your environment. For some examples consult our Recommended Information
Generally, no. the average network load per scanned system is around 400kb.
Generally, no. However, some combinations of operating systems and scanning patterns may have a measurable impact on the remote system.
We do not recommend to use the Discovery-Tool on a system that provide any other services. The Discovery-Tool needs to handle a lot of objects and will use a lot of the system memory.
The change from collecting ESXi informations from SSH or SNMP to the provided Web-Api can result to new Object Hashes for the ESXi Host System.
This is related to the issue that the attribute "Serial Number" can not be collected in some cases. We apologise that and we hope that this issue will be fixed by VMWare.
You have two options to handle that situation:
If the "old" ESXi-Object(s) are not used for connected JIRA-Issues you can delete the "old" ESXi-Object(s)
If you want to use the "old" ESXi-Object(s) copy the ObjectHash Value from the "new" ESXi-Object to the "old" ESXi-Object.
Now you can delete the "new" ESXi-Object and the "old" one will be updated in future.
We had to upgrade the Assets Discovery add-on to 2.9.3 in order to to add some minor fixes. The Tool was not included in this update. However, it should work normally with the updated add-on. We will fix the version numbers in both the tool and add-on to be aligned soon.
In version 2.9.2 or higher, If the License generated by Assets Discovery in Jira - to license your Discovery Tool (License starting with "Vv...") is showing a Lower Tier than the Tier you've purchased, it might be due to the Universal Plugin Manager being outdated.
To resolve this, please navigate to Jira Administration>Add-ons>Manage Addons–> "Atlassian Universal Plugin Manager Plugin" and update the UPM to the latest version available, then Disable and re-Enable Assets Discovery. This will generate a new License to be used to license the Discovery Tool correctly.
If your RSA Key is generated with OpenSSH version > 7.8 the key will not work with the used SSH.Net Library.
This is a known Bug that you can track here: SSH.Net Bug 485
You can use the "-m PEM" Option for your RSA Key generation.
We are mention in every release note if the Assets Discovery release contains a new Windows-Agent.
If the Discovery-Tool is receiving result data from an "older" Windows-Agent is can happen that the result structure is not compatible.
In that case the Discovery-Tool can not deserialise the xml data and you will see exception in the log file like:
1
2
Error reading NetworkCommands.
Object of type 'System.Boolean' cannot be converted to type 'System.String'.
Yes, we recommend to create a "Discovery"-User which is used to connect to the systems.
Please take a look to technical solutions called LDAP or Active Directory to prevent adding hundreds of "single"-credentials to the Discovery-Tool
For SNMP Pattern you need to know which OID contains the data that you like to assign to the Assets Object.
The OID Values can be assign to the "default"- Object properties of a Discovery Info Class or can be used for Extended Information of a Discovery Info Class.
To include the OID in an SNMP Walk you need to add the parameter "-O n" to the SNMP Walk command.
snmpwalk -v1 -O n -c public 192.168.178.60 .iso > walk_out.txt
First try to use the "Discovery.exe -u" command.
If the service is still in the List of Windows Services:
Open a Command Prompt and execute the following command with your exact Service Name.
After restarting the system the service is uninstalled.
1
sc delete [service name]
Was this helpful?