Transcript
Radar to bring assets into your environment, and we'll cover those in this video. The first step is to configure asset layout mapping, which you can do by going into Admin and into Hudu Radar. Once you've mapped an asset layout to a Radar device type, you'll be able to connect fields in that layout to Radar data points. As you can see here in my Radar settings, I have Workstations mapped to my Workstations asset layout, Switches to my Switches asset layout, and so on. If you didn't want to bring in a particular device type at all, let's say mobile devices, we would just leave this box blank. And if you wanted multiple device types to land in the same asset layout, let's say network devices, we could go ahead and specify that here. The other thing you'll need to do in this section is state your device requirements. Selecting these requirements essentially means that any device that doesn't meet all of them will not be sent to Hudu. If you have certain device requirements that are not set, but Radar still detects them, they will still populate as fields inside of Hudu. So now that we have the asset layout mapping done and the device requirements set, let's go ahead and jump into our asset layouts. Here we can see how the asset layouts actually connect to Hudu Radar. This asset layout is already set up and is in use for Hudu Radar, as you can see from this banner above. Right now, rich text and text fields are the only fields that can be used for Radar data points. Here in my IP address field, there is a sources section with a dropdown to select a Hudu Radar data point. I've selected IP address from that dropdown to tell Radar this is the field I want it to populate. A quick tip for you, most data points are going to be best served with the text field type, but data points that should use rich text such as CPUs, disks, and interfaces often come back as a bulleted list of values. One thing to keep in mind, if you make a Radar data point field required, the asset will only be created once Hudu Radar is able to complete that field. If Radar can't complete a required field, the asset won't be created and the device won't be sent to Hudu. Another way to leverage Hudu Radar is the ability to automatically create warranty expirations. Using my warranty expiration field here, I can select the date field type and check the box to automatically add it to the expirations list and to use Hudu Radar to create a warranty expiration if vendor and serial numbers are found for a device. That's everything you need to get your asset layouts created and set up to start syncing in Hudu Radar devices. As soon as you've done this, check out the next video in this Hudu Radar series where we'll cover managing the devices that Radar actually brings in. Thank you all so much for joining, if you do have any questions, feel free to reach out to us at support.hudu.com or leave a comment below.
