Between sharing your Network Atlas maps and Worldwide maps, you've all helped us out as we continue to improve the Orion maps. Which is why we want MORE! Show us your Orion Maps (or at least the ones you cannot live without) OR email it directly to me at firstname.lastname@example.org AND answer the following questions, then we'll award you 500 thwack points. (You must answer the questions as well as share your maps to get points)
Please submit your maps by December 31, 2019 to receive 500 THWACK points.
This version is getting better! but I think it's still lacking some basic features. Some have mentioned previously, but I'll toss my votes in for the following:
Callahan - thanks for sharing feedback!
- Edit the line shape/format/color - JB - When you say "shape" of the connector - I assume you are referring to being able to create right angles or curved connections. We know this is important for reasons such as data density and something we hope to allow users to be able to do in a future release. I am trying to get this accomplished sooner than later. If you have any screenshots for what a "Clean Flow" looks like for you - I would love to see an example of it. Also curious what you would want to adjust color of the lines for? Do you not want these connections representing status conditions? The goal is to have some standardization there so curious what your thoughts are here as well.
- Heat Maps - JB - this is not something on the short term roadmap for the Orion Map project, but I know something jason.carrier is very interested in finding out if this feature is still valuable in your organization.
Thanks jblankjblank! in response to the bolded.
Correct on the right angle/curved connections, that'd be nice! But also the weight/thickness of the connector line as well. There are quick thick by default and can create overlapping portions when you have multiple connectors on an object. As for colour coding, I've used them differently in various organizations as a quick visualizer for things like bandwidth on links, different colours for 1/10/25/40/100 gb links (at their request). I've also used them to to display active/failover paths as well.
Heat Maps, we use currently use it, but not to what I think could be the full potential of it. If you're a Cisco shop, I think the DNA center appliance will cover a lot of these...but that's expensive. But if you're looking to offer some of that functionality, things like being able to see the AP that a user is connected on, and the current signal strength, along with historical session data (so you can capture the "It didn't work yesterday" type requests). Those would be handy!
Hey Michael - Thanks for your feedback on wireless heatmaps. If you've got some time, I'd love to jump on a call to discuss. Tracking where users and devices are connected to wireless networks is something I'm researching at the moment.
Here is a portion of a map I am working on. I really like that I can create manual connections between interfaces like I have done below, but I would like to have the discovered connection be removable, or have the option to aggregate the traffic stats from both manually defined connections. You can see that the discovered connection is using the stats from 1/0/9 and 1:1. When there are multiple discovered connections, it seems to choose just one and show the stats for it.
That is correct Adam - when there are multiple connections between two nodes, we consolidate those into a single line. What will be bubbled up to the top will be the connection with the worst status, based on hitting a threshold. There could be multiple types of connections between two entities, and some of our larger customers have quite a bit. The preference at times across many of you have been to show me when something is wrong, don't inundate me with every detail in my face at all times. Would you prefer to see all connections vs the rolled up status? If so, how would you envision that working?
What I would like to see if I am unable to hide the auto generated link, is the total from all links. As you can see in the picture it just shows the data from ten 1/0/9 to port 1:1, and does not include the traffic from 2/0/9 to 2:3.
The map should be showing 233.3 Mbps from the left switch and 174.49Mbps on the right switch.
Yes we still currently use Network Atlas because Orion maps cannot meet our needs.
All Maps must be legible when in NOC view. Orion maps on a projector for NOC view is impossible. It’s too busy cannot change anything. We also monitor temp for Datacenter. This is monitored from the Custom MIB Poller that is integrated into Network Atlas. We need to be able to create icons for L3 Encryptors and then assign them to an interface without monitoring the device in Solarwinds as a node.
The main issue with Orion Maps are the Lines. I cannot change the Color, Size and Type. I need a map to reflect Tunnels (Dash Line), Direct Connections(Solid Line), and Link size(Thicker line), Black Line for up status not Green.
I also need to have cloud or any icon to show remote sites and then be able to click remote site to see their architecture. (This is the nested Maps)
I have tried to recreate maps in Orion Maps and have not been able to get the detail and formatting that I can get in Network Atlas.
Also I am unsure if I can display custom properties
I have tried to recreate some of my maps and ended up very disappointed with the results. My biggest issue is with the ability to control the layout of the connections.
Great information here. Really appreciate the feedback! Clearly manipulating the layout of the connections is important and understood. This is something we are working on. Also using custom icons, adding text boxes, shapes, etc... Are you manually labeling each of the interfaces to the short name? Are each of these connections manually drawn, and thus don't change based on status? Just hoping to understand more of what might be useful. Looks like an awesome map but likely not the easiest to maintain either, correct?
Love the Table based map too - can you elaborate a bit more on what you are doing here and where you are getting the data from so I don't guess? It looks like a break down of services and values/ status from different associated elements.
Happy to jump on a call if its easier.
It's done the same as this sample map in SAM along with custom labels which contain variables.
That's the beauty about Network Atlas, it's super flexible. If you are monitoring it, you can display it in map format.
rocco_2016 Thanks for your input! Quick question; Since custom labeling is important to you, can you elaborate on what ideal behaviors would be incorporated that would knock this out of the park? What do you need to be able to do? Is this adding more metadata under neath the entity for example? What type of metadata are you looking to see? What else?
I have recently been working around this limitation for a requirement by the business. I have a remit to be able to show Topology dashboards with the ability to easily show (label) the device type. ie Firewall, Router, Access switch etc. So when this maps are used as a NOC. It will allow support with little knowledge of networks quickly identify the device type. With the new 2019.4 version. I can add labels by the way of images as a work around. But I'm being forced to use Atlas Maps to have these device type labels. Thanks
We are (finally) in the active process of migrating from NPM version 10.6 to the latest stable release, around v12.5. The old version currently in production only has Network Atlas, and I have used the Orion Maps module in the proof of concept and development instance here at work. Addressing the questions below inline.
1. Share your map(s) below or email it to email@example.com
A: Shared below- this is one example of one site which intrinsically helps us identify very quickly the status of a site, including WAN/LAN, and wireless.
2. Are you still using features from Network Atlas that you NEED to have in Orion Maps?
A: We are using both, but only int he sense of migration to ensure we can leverage same functionality in old AND new. There do no seem to be any dependencies necessarily that we are not getting with the new existing in the old.
3. Why is a feature like Maps or Atlas important to you and your organization? What if you didn't have this feature?
A: Mapping is one way to visually bring context to the information and status that monitoring presents. Orion Maps and Atlas both have played and will play a pivotal role, without which we might not have the same comprehensive view or context.
kingslider Very interested indeed! Would love to jump on a call to discuss your use of the wireless heatmaps feature, and NPM's roadmap for wireless network monitoring. I'll follow up with a private message.
Thanks kingslider great feedback! Now your image is an interesting one as this is clearly a wireless heat-map. That functionality is not on the current road map for Orion Maps. Curious how critical this is to you and the community and whether the wireless heat-maps are heavily leveraged across the board. This is something that jason.carrier is very interested in.
Was just doing today's mission question when I noticed this in the demo (https://oriondemo.solarwinds.com/Orion/SummaryView.aspx?netobject=&ViewID=491)
Someone needs to tell whoever set the page up that there's a wonderful new feature called Orion Maps!
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.