{"_id":"56a208590067c00d00a2f956","__v":13,"project":"56a1f77442dfda0d00046285","version":{"_id":"56a1f77542dfda0d00046288","__v":9,"project":"56a1f77442dfda0d00046285","createdAt":"2016-01-22T09:33:41.397Z","releaseDate":"2016-01-22T09:33:41.397Z","categories":["56a1f77542dfda0d00046289","56a1fdf442dfda0d00046294","56a2079f0067c00d00a2f955","56a20bdf8b2e6f0d0018ea84","56a3e78a94ec0a0d00b39fed","56af19929d32e30d0006d2ce","5721f4e9dcfa860e005bef98","574e870be892bf0e004fde0d","5832fdcdb32d820f0072e12f"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"parentDoc":null,"category":{"_id":"56a20bdf8b2e6f0d0018ea84","pages":["56a20e302255370d00ad5ecb"],"project":"56a1f77442dfda0d00046285","__v":1,"version":"56a1f77542dfda0d00046288","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-01-22T11:00:47.207Z","from_sync":false,"order":3,"slug":"features","title":"Features"},"user":"56a1f7423845200d0066d71b","updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-01-22T10:45:45.499Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"## Why is it helpful?\n\nOn the service map you can check how your services communicate with each other, what are the average response times and how many requests each service makes. See the communication with databases and 3rd party APIs, and get live hints when your services are getting slower.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Discover bottlenecks\",\n  \"body\": \"Our Topology feature automatically highlights negative differences in your infrastructure. Watch for the info icons to discover and prevent issues in your system. Do you want to be the first who knows about them? No problem, [setup alerts](/docs/alerting) and get notified via your favorite channels like Slack, email and Pagerduty.\"\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/4b9bd37-topology.png\",\n        \"topology.png\",\n        3360,\n        1704,\n        \"#2a4b6a\"\n      ],\n      \"caption\": \"Service map with demo services and ongoing incident\",\n      \"border\": false\n    }\n  ]\n}\n[/block]\n## What's in the picture?\n\nOn the picture, you can see the demo infrastructure's service map. Nodes with the info icon mean that something is different from the usual. Like response time is 20% slower compared to the last period. The red node means that an ongoing incident is happening like a critical memory usage.\n\nWith our topology view you can quickly see throught your services, databases and their conditions.\n\n## Things you can do:\n\n- Move or zoom the graph.\n- Reposition the nodes by dragging them around.\n- Click on an element to view details about it.\n\n## Map legend\n\n- Nodes with red or yellow colors show ongoing incidents.\n- A node with the (i) sign contains hints based on its performance.\n- Red or yellow colored arrows show ongoing problems with a transaction.\n- Arrows 'width and nodes' size increase with more requests.\n\n## Detailed node view\n\nClick on a node to access detailed information on a given service. The opening panel contains basic metrics and links to relevant incidents. Trace provides additional hints when a performance issue is discovered.\n\n## Detailed transaction view\n\nClick on an arrow to access detailed information on a given transaction. The opening panel contains links to relevant metrics and incidents. Get hints based on the health of a connection.\n\n## Layers of information\n\nActivate any layer of information to display different metrics.\n\n- Ongoing incidents: Activate to color nodes and connections based on their health.\n- Response times: Activate to show the response times of your services.\n- Network delay: Activate to show the network delay of each connection.\n- Request count: Activate to show request per minute numbers between your services. Services and connections handling more requests will become bigger.\n\n## Service types displayed\n\nShow or hide databases and 3rd party APIs in order to achieve a service map with better visibility.\n\n## Auto update\n\nActivate to refresh the topology automatically every minute.\n\n## Layout\n\nYou're able to reset nodes position by using a predetermined algorithm, or revert the map to its last saved state.\n\n## Time selector\n\nUse the time selector dialog to view how your microservices' map looked like at a given time.","excerpt":"Visualise your services status and communication.","slug":"topology-view","type":"basic","title":"Topology view"}

Topology view

Visualise your services status and communication.

## Why is it helpful? On the service map you can check how your services communicate with each other, what are the average response times and how many requests each service makes. See the communication with databases and 3rd party APIs, and get live hints when your services are getting slower. [block:callout] { "type": "info", "title": "Discover bottlenecks", "body": "Our Topology feature automatically highlights negative differences in your infrastructure. Watch for the info icons to discover and prevent issues in your system. Do you want to be the first who knows about them? No problem, [setup alerts](/docs/alerting) and get notified via your favorite channels like Slack, email and Pagerduty." } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/4b9bd37-topology.png", "topology.png", 3360, 1704, "#2a4b6a" ], "caption": "Service map with demo services and ongoing incident", "border": false } ] } [/block] ## What's in the picture? On the picture, you can see the demo infrastructure's service map. Nodes with the info icon mean that something is different from the usual. Like response time is 20% slower compared to the last period. The red node means that an ongoing incident is happening like a critical memory usage. With our topology view you can quickly see throught your services, databases and their conditions. ## Things you can do: - Move or zoom the graph. - Reposition the nodes by dragging them around. - Click on an element to view details about it. ## Map legend - Nodes with red or yellow colors show ongoing incidents. - A node with the (i) sign contains hints based on its performance. - Red or yellow colored arrows show ongoing problems with a transaction. - Arrows 'width and nodes' size increase with more requests. ## Detailed node view Click on a node to access detailed information on a given service. The opening panel contains basic metrics and links to relevant incidents. Trace provides additional hints when a performance issue is discovered. ## Detailed transaction view Click on an arrow to access detailed information on a given transaction. The opening panel contains links to relevant metrics and incidents. Get hints based on the health of a connection. ## Layers of information Activate any layer of information to display different metrics. - Ongoing incidents: Activate to color nodes and connections based on their health. - Response times: Activate to show the response times of your services. - Network delay: Activate to show the network delay of each connection. - Request count: Activate to show request per minute numbers between your services. Services and connections handling more requests will become bigger. ## Service types displayed Show or hide databases and 3rd party APIs in order to achieve a service map with better visibility. ## Auto update Activate to refresh the topology automatically every minute. ## Layout You're able to reset nodes position by using a predetermined algorithm, or revert the map to its last saved state. ## Time selector Use the time selector dialog to view how your microservices' map looked like at a given time.