Cool and intuitive service infographics

We’ve introduced a major revamp to our service infographics. In addition to being more streamlined, the service infographics now convey details about queues and messaging services.

Web request services

The web request service infographic has undergone the most change. As you can see, we still separate Resource requests from Dynamic requests, but the design now includes intuitive browser-style tabs to differentiate between the two resource types. Also worth noting is that the load elements on the left (Resource requests/min from Dynamic requests/min) are no longer clickable.

Queue support

We’ve adapted the service infographic design to convey queue support. Any service that either sends messages to or pulls messages from a queue includes a Queues icon on the right of the infographic. This gives you easy access to all queues that a given service uses. Note that the arrows between the main part of the infographic and the Queues icon tell you if the service is sending messages, receiving messages, or both. In the example below, the Customer Frontend is sending to one queue and receiving from a second queue.

We’ve adapted the messaging service infographic in the same way to show how each messaging service listens and processes messages. Although a service typically only listens on a single queue, there can be setups where a messaging service listens on multiple queues. As you can see in the example below, the Hot Deal Provider messaging service listens on one queue, receives two messages per minute, and sends messages to another queue.

All other service infographics…

To maintain a consistent look and feel, all infographics have been adapted in a similar way, as you can see below:

Those who know me know that I'm passionate about 3 things: rock climbing, physics, and performance.
I've worked in performance monitoring and optimizations in enterprise environments for the better part of the last 10 years. Now as a Product Manager I am doing my best to build those experiences into Dynatrace.