Summary
Related design issue elastic/apm#300
The service overview introduces a new view for the selected service that encompasses a lot of the service data from existing views like metrics, transactions, and errors. The primary goal of the view is to aid in troubleshooting a service from a birds eye view rather than immediately diving into the Transactions, as that's the current landing page for a selected service. There's more information about the user stories and goals of the view in the design issue linked above.
Dependencies table
One of the new components of the view is the dependencies tables that list the downstream services or external connections that are relevant for the service at the selected time range. The information stems from the destination data captured for the service map. In this component, we're not only listing the connections but also showing the metrics per connection such as latency, traffic, and error rate.
Per #81120 (comment), we are not going to include the health status.
Summary
Related design issue elastic/apm#300
The service overview introduces a new view for the selected service that encompasses a lot of the service data from existing views like metrics, transactions, and errors. The primary goal of the view is to aid in troubleshooting a service from a birds eye view rather than immediately diving into the Transactions, as that's the current landing page for a selected service. There's more information about the user stories and goals of the view in the design issue linked above.
Dependencies table
One of the new components of the view is the dependencies tables that list the downstream services or external connections that are relevant for the service at the selected time range. The information stems from the
destinationdata captured for the service map. In this component, we're not only listing the connections but also showing the metrics per connection such as latency, traffic, and error rate.Per #81120 (comment), we are not going to include the health status.