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

1)

2) I think the main things I still use in Atlas that I couldn't do in the new maps are custom labels, custom tooltips, and being able to select and delete connections that I don't want the map to display.  Would be good to just have some kind of "hide this connection" at least.

3)  I find that the main value add in building these maps is it provides a way for someone who knows how everything comes together to document that and make it accessible to the rest of the team.  I may know all the critical interfaces for my WAN topology but the new hire hasn't learned them yet and it's a lot easier to point them to a WAN dashboard in Orion than to actually sit down and explain all the bits every time.  Similar problems apply to application architectures.

1)

2) I think the main things I still use in Atlas that I couldn't do in the new maps are custom labels, custom tooltips, and being able to select and delete connections that I don't want the map to display.  Would be good to just have some kind of "hide this connection" at least.

3)  I find that the main value add in building these maps is it provides a way for someone who knows how everything comes together to document that and make it accessible to the rest of the team.  I may know all the critical interfaces for my WAN topology but the new hire hasn't learned them yet and it's a lot easier to point them to a WAN dashboard in Orion than to actually sit down and explain all the bits every time.  Similar problems apply to application architectures.

mesverrum​ - more on your point 3 - you can share that map with your NOC and that will make those connections obvious (for lots of teams). So when something goes red, its not just noise.