Ask HN: Visualizing your web service intereactions

I am often amazed at how teams use/misuse UML to explain to newer members how their web service interacts in an ecosystem with other services and shy away from maintaining a proper UML sequence diagram if the service is very complex. Sometimes, people end up using simpler abstractions and build diagrams using something like websequencediagrams.com but those can sometimes be a hit or a miss depending on the nature of what you're trying to express.

Culturally, every team ought to set the right documentation that is easily updatable in the face of an evolving architecture, so my question to the HN community is, what tools do you use in your team to document your service interactions? Has anyone here built any of their tools that help better "visualize" their web service interactions to help ramp new members? Bonus: Is there any known open source tool to build your diagrams with a baked-in "animation" (like a GIF'd version of the sequence diagram) that captures interactions (perhaps by annotating/scaling calls with SLAs) and other nuanced behavior (parallel calls, queueing, async responses).