JupiterOne
Integrations that know about the same physical device have conflicting _type mapping (`hardware`|`user_endpoint`)
The Stethoscope agent and CarbonBlack sensor map to a target entity of _type: 'user_endpoint' while the Snipe-IT integration maps to _type: 'hardware'. Ideally, we'd see a single entity known to Snipe-IT and monitored by those agents.
Discussion IRL...
It has been suggested that the _type value should be user_endpoint ONLY IF there is ample data in the Snipe-IT asset to determine that it is in fact an endpoint delivered to a user, such as a laptop or tablet. Or perhaps there is enough information to make it _type: 'computer'. It has also been suggested that if there is enough information in the asset, _type: 'ios_device' or _type: 'android_device' (or something like that) should be used. We need to work through a clear definition of the meaning of _type.
We need to be working toward having a single entity in the graph for a Device that is the same object in the universe.
