Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Adding Maps to a View - Video

Adding Maps to a View - Video

Updated March 11th, 2016

Overview

This video will demonstrate how to add a Network Atlas map to the Orion web UI and how to re-size the map.

 

 

 Environment

Orion Platform v2016 and above

             

Server & Application Monitor  v6.2.4 and above

Network Performance Monitor v12 and above

Virtualization Manager

Network Traffic Analyzer         

Storage Resource Monitor  

Network Configuration Manager 

Web Performance Monitor

IP Address Manager

User Device Tracker                                                        

VoIP & Network Quality Manager

Video Transcript

In a previous video I covered building maps with Network Atlas. Now I’ve decided that I want to add one of my maps to my current view.


I’ve already added the map resource to the view, but as a reminder, let me look at the view editor. The resource you’ll need to add a map from Network Atlas to your view is simply called ‘map.’


When you preview the view, you’ll basically see a placeholder where your map will sit.


So now to add the map, I’ll click on edit. In the map resource editor I can see a list of all the maps I’ve built in Network Atlas. I’m going to choose the map called global Network Map and click submit to add it to my view.


But I seem to have a problem. You’ll notice that my map is too big to fit in the column. Remember that your view columns and your maps are both fixed pixel width. Neither one is going to scale to match the other. If you’ve got enough screen real estate to resize your columns to match your map, fine. But if not, then you’d have to scale down the map.
I’m going to go back to the editor and scale my map down to 85% to make it fit and click submit.


But notice that when you scale the map down, everything scales down. My labels are too small to read. My icons are almost too small to click. And there’s nothing I could do at this point except start from scratch with a new map.


Scaling maps works great for fine tuning the exact size of your maps and columns, but doesn’t work so well if you try to go too far. So as I’ve said before, when you’re building your maps, plan ahead. Build the map to match the column sizes of your view.
 
While I’m here, notice the check box for turning the network atlas download link on or off so you can grant or restrict the ability of other Orion users to create their own maps.


So now let me submit one more time, and when I come back to my view, I’ve got my map, and it’s sized appropriately so I can see all my labels and the object status icons. When I hover over the object icons, I can see details about the object, and I can also click the icon to drill down into the object.


So building maps is simple, adding maps to your view is simple, but planning out your maps is critical.

Last modified
09:25, 3 Mar 2017

Tags

Classifications

Public