You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Service instances view
The goal of breaking service performance performance into each instance is to allow easily identifying whether service is experiencing problems across all instances or if only some of them are affected.
This could be related problems like deployments, geo locations, issues with infrastructure or network, etc.
Default breakdown would leverage break down by service.node.name.
This issue is to track research and development of this component, including all work it depends on.
As a test, I attempted to create a similar visualization using canvas using its scatter plot chart on dev-next.
The text was updated successfully, but these errors were encountered:
Summary
Related design issue elastic/apm#300 and part of meta issue.
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.
Service instances view
The goal of breaking service performance performance into each instance is to allow easily identifying whether service is experiencing problems across all instances or if only some of them are affected.
This could be related problems like deployments, geo locations, issues with infrastructure or network, etc.
Default breakdown would leverage break down by service.node.name.
This issue is to track research and development of this component, including all work it depends on.
As a test, I attempted to create a similar visualization using canvas using its scatter plot chart on dev-next.
The text was updated successfully, but these errors were encountered: