Help with Assets Discovery and it's relationship to CSV imports
- Replies 1
- Views 417
- Created
- Last Reply
Top Posters In This Topic
-
Jimi Wikman 1 post
Popular Days
Most Popular Posts
-
I have never used the discovery tool myself, so I can't give you hands-on experience there :) Based on the information on the Atlassian website (not sure if that is accurate or not), there are certain
Adrian Rutt was awarded the badge 'Curious Mind'
So I am doing an assets implementation and, for the first time, using assets discovery tool with CSV imports. My question (if I understand the discover tool correctly) is how the results of the discovery tool scans relate to and interact with everything else that I imported manually through CSV. The person who taught me about the discovery tool said basically to keep "duplicates" of IT devices: one that is the result of the scan (super in depth attributes) and one that is for use with connecting to service management stuff.
For example, Laptop 1 would have an entry in my discovery Schema as well as an entry in another IT Assets Schema. The latter would be for general connections to service management, but the former would be if the IT helpdesk would need more in depth details about Laptop 1. My question is whether this is correct. It sounds incorrect to me, but I see why someone would set something up this way i.e. the attributes for service management connections to a helpdesk are usually very different than the kinds of attributes needed for deep IT work on those devices. Second, is there a way to connect the two that is more streamlines or best-practice oriented? The person who taught me suggested to forge references between schemas, but then when I asked if those references would all be wiped on the next discovery import, they said yes, so that seemed odd.
I'm a little lost and not even sure if my questions makes sense. Any help is greatly appreciated!