{"_id":"56a20a2a8b2e6f0d0018ea80","user":"56a1f7423845200d0066d71b","__v":3,"parentDoc":null,"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"},"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"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-01-22T10:53:30.858Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":2,"body":"## Why is it helpful?\n\nUsing this page you can easily spot the transactions that caused errors in your system.\n\nUsing this view you can easily spot what the errors were in a transaction, where they occurred, check the timings (*) and what other services it affected.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Distributed tracing\",\n  \"body\": \"Finding issues in a distributed system or microservices can be challenging. Trace by RisingStack comes with an automated transaction tracking features. We collect, group and visualize your service calls with issues. Don't waste your time with spending hours to dig in your logs, just visit our trace feature.\"\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/f651e64-distributed-tracing.png\",\n        \"distributed-tracing.png\",\n        1916,\n        880,\n        \"#234058\"\n      ],\n      \"caption\": \"Distributed tracing - finding an issue in a microservices transaction\"\n    }\n  ]\n}\n[/block]\n## How does this work?\n\nTrace gathers the full transaction of requests across your services. The transactions or \"traces\" that contain errors will be displayed here.\n\n## Things you can do:\n\n### List ongoing issues\n\n- visualise a trace by clicking its \"view\" button\n- directly visualise a trace if you know its request Id\n- search for a particular error using different filters.\n- try this trace sample example.\n- What you are seeing:\n\n- The services that responded with an error during the transaction, including the status code. \n- The request that started the whole transaction. (Root request)\n- When the problem happened for the last time and how many times.\n\n### Visualize specific transaction\n\n- Move the graph; click the background and drag.\n- Use the sliders to scale the graph; top left of the screen. 1:1 to reset.\n- View detailed event information. Click the colored dots on the graph. (if any)\n- View a list with all events. (requests, responses)\n\n#### Indicators\n\n- A red dot indicates an error event.\n- A blue dot indicates some information of interest.\n- A greyed request indicates that it was not reported by the Trace Collector.\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"body\": \"The timings depend on the time in your different hosts. In some rare cases you might see negative network delays because of this.\",\n  \"title\": \"Timing\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"body\": \"The host may be displayed instead of the service name when the service failed to report.\",\n  \"title\": \"Hostname\"\n}\n[/block]","excerpt":"Discover errors spread across your distributed services.","slug":"trace-view","type":"basic","title":"Trace view"}

Trace view

Discover errors spread across your distributed services.

## Why is it helpful? Using this page you can easily spot the transactions that caused errors in your system. Using this view you can easily spot what the errors were in a transaction, where they occurred, check the timings (*) and what other services it affected. [block:callout] { "type": "info", "title": "Distributed tracing", "body": "Finding issues in a distributed system or microservices can be challenging. Trace by RisingStack comes with an automated transaction tracking features. We collect, group and visualize your service calls with issues. Don't waste your time with spending hours to dig in your logs, just visit our trace feature." } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/f651e64-distributed-tracing.png", "distributed-tracing.png", 1916, 880, "#234058" ], "caption": "Distributed tracing - finding an issue in a microservices transaction" } ] } [/block] ## How does this work? Trace gathers the full transaction of requests across your services. The transactions or "traces" that contain errors will be displayed here. ## Things you can do: ### List ongoing issues - visualise a trace by clicking its "view" button - directly visualise a trace if you know its request Id - search for a particular error using different filters. - try this trace sample example. - What you are seeing: - The services that responded with an error during the transaction, including the status code. - The request that started the whole transaction. (Root request) - When the problem happened for the last time and how many times. ### Visualize specific transaction - Move the graph; click the background and drag. - Use the sliders to scale the graph; top left of the screen. 1:1 to reset. - View detailed event information. Click the colored dots on the graph. (if any) - View a list with all events. (requests, responses) #### Indicators - A red dot indicates an error event. - A blue dot indicates some information of interest. - A greyed request indicates that it was not reported by the Trace Collector. [block:callout] { "type": "warning", "body": "The timings depend on the time in your different hosts. In some rare cases you might see negative network delays because of this.", "title": "Timing" } [/block] [block:callout] { "type": "warning", "body": "The host may be displayed instead of the service name when the service failed to report.", "title": "Hostname" } [/block]