Show us your Network Atlas maps!

[shuckyshark]

With being responsible for such a large geography, with very unstable and limited internet access, it’s important to keep on top of connectivity issues. This helps us spot problems before they become critical…

[HumanK]

Emailed.

We use the main world map to show our subsidiary offices status when you login to Orion.

[rstewart1]

Emailed!

[designerfx]

I love atlas for it's capability but it's limited by module - so if you don't have the modules you need, you can't truly map things out the way they could be done.

Atlas can/should be one of the shiniest toys to wave front and center but as grantallenby​ rightfully points out, it needs a lot of love. I'll email you some good stuff, kbongi​ (email sent).

kbongi​​ this is definitely something a lot of our staff would probably have an interest in seeing what is to come, it might be a good way to build some hype as we try to get them to look at the appstack bundle (assuming some of what's coming is relevant).

[jczes]

Emailed

[yaquaholic]

The only map we have that isn't littered with customer details.

But I would have to conclude, Atlas is long overdue an update, it is slow and cumbersome.

Filtering would be rather handy, other products I have used, have the ability to only display elements (on the map) that meet the criteria, such as node down, or CPU busy or status <> up.

So you create a map with all devices in it and they only show up if there is a problem with them.

[CourtesyIT]

Awesome,  The previous one is a great resource for ideas and such. 

Show us a NOC view and get 500 thwack points!  This is the old Map contest.

[zackm]

email sent with some screenshots of a recent one I am particularly fond of

Common comments/complaints/requests from Students and Clients:

1. Slowness of Network Atlas (NA)
2. "Antiquated" GUI
3. Lack of one-way interface utilization color-coding (currently you must be monitoring both ends of a point-to-point link to get color-coding in NA; very painful for MPLS networks)
4. Lack of easy customization options for stencils/icons
5. Lack of container objects (a la Visio)
6. Lack of flowchart objects (a la Visio)
7. UnDP objects do not show the status per threshold/value, but the status of the ability of SW to poll an OID. (e.g.; if I have a UnDP that measures battery status on a UPS, the NA icon would be green as long as the SNMP query worked, no matter what the actual returned value was/is)
8. Lack of grouping options for objects / hard to find specific data points to add to a map
9. No search option in NA to find objects
10. Lack of relational awareness like we have now in PerfStack ("Add all related entities" button) / No tie-in to AppStack
11. ConnectNow is painfully inaccurate
12. Lack of auto-mapping based on Orion Dependencies (If the dependency is mapped in my database, why can I not click a button to add the objects to NA?)
13. Lack of NA Tooltip variables at the same level that we have with the Web Alert Engine (all variables from SWIS should be accessible, including "Create a variable from SQL")
14. Lack of "Preview" option in the NA app; to see the "real" map you have to add it to the Orion site and then go back and forth to edit small changes (usually in the area of those tooltip variables from 13)
15. Wireless Heat Maps for more vendors than just Cisco (Meraki, Aruba, Ruckus, Huawei, Ubiquiti are all top Enterprise WLAN Vendors across FY2016 based on market revenues, but only Cisco WLCs are supported in heat maps)

There's probably some more, and I will add them if they pop into my head, but the items above seem to be universal thoughts across almost every engineer I train on Network Atlas.

-ZackM

Loop1 Systems: SolarWinds Training and Professional Services

• LinkedIN: Loop1 Systems
• Facebook: Loop1 Systems
• Loop1 Twitter: @Loop1Systems
• ZackM Twitter: @ZackM

[nickzourdos]

Hear, hear!

[RaviK]

Great points zackm​