This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Before the decade ends, show us your Orion Maps AND answer a few questions about them -- for 500 THWACK points!

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 kristin.bongiovanni@solarwinds.com 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)

  1. Share your map(s) below or email it to kristin.bongiovanni@solarwinds.com
  2. Are you still using features from Network Atlas that you NEED to have in Orion Maps?
  3. Why is a feature like Maps or Atlas important to you and your organization? What if you didn't have this feature?

Please submit your maps by December 31, 2019 to receive 500 THWACK points.

Parents
  • Hi,

    a few maps :

    map4.jpg

    map1.jpg

    map3.jpg

    2.     In Orion Maps, I'd like a similar scalability to Network Atlas. Line types - broken/angled line.
    I do not need Icons, I prefer to see node status for the first look, so simple graffic is enough

    Well definable dependence of maps, which did not work well in Atlas. I'd like to transfer status between nested maps only in a specified direction - for example, from a hierarchically subordinate map to a parent map, but not vice versa.

    This makes it easy to trace a network fault - I simply follow the alarm "red" color from a higher-level network infrastructure map to a lower-level map (from core through distribution to access).

    3.     The map is one of the most important things we use, it provides a simple insight into the topology of the network, and humanly shows the dependencies of the individual elements of the network.
    The map simplifies troubleshooting, development planning, simply everything is a very,very,very important tool.

    My work is basically impossible without maps.

Reply
  • Hi,

    a few maps :

    map4.jpg

    map1.jpg

    map3.jpg

    2.     In Orion Maps, I'd like a similar scalability to Network Atlas. Line types - broken/angled line.
    I do not need Icons, I prefer to see node status for the first look, so simple graffic is enough

    Well definable dependence of maps, which did not work well in Atlas. I'd like to transfer status between nested maps only in a specified direction - for example, from a hierarchically subordinate map to a parent map, but not vice versa.

    This makes it easy to trace a network fault - I simply follow the alarm "red" color from a higher-level network infrastructure map to a lower-level map (from core through distribution to access).

    3.     The map is one of the most important things we use, it provides a simple insight into the topology of the network, and humanly shows the dependencies of the individual elements of the network.
    The map simplifies troubleshooting, development planning, simply everything is a very,very,very important tool.

    My work is basically impossible without maps.

Children
No Data