Tracking down bugs in distributed systems can be really difficult. One of the technologies we’re using in Indigo to help make this easier is known as “E2E Tracing” (for End to End Tracing). Of course, this technology is only as good as the traces that a system emits. In Beta 1, we weren’t so good about our traces, but in the past few months we’ve made a concerted effort to improve them. And we need your feedback on what is easy to track down and (just as importantly) what was a pain in the butt to figure out. I recommend starting at “Warning” level. Verbose traces are very, well, verbose and can often be hard to navigate through.<\/p>\n
Indigo also includes a Trace Viewer (svcTraceViewer.exe) which allows you to make heads (or tails) of the Xml files that are generated. Again, feedback on the tool is highly encouraged.<\/p>\n
Here’s a sample config file snippet that will enable tracing in Indigo Applications and will generate Xml file with the traces.<\/p>\n
The generated file can then be opened with svcTraceViewer.exe<\/p>\n
<configuration>\n <system.diagnostics>\n <sources>\n <!-- The 'switchValue' determines the level of traces that will\n be outputted, e.g. 'Verbose', 'Warning', 'Error', etc -->\n <source name=\"System.ServiceModel\" switchValue=\"Warning, ActivityTracing\"\n propagateActivity=\"true\">\n <listeners>\n <clear \/>\n <!-- The 'initializeData' attribute determines to which file\n the traces will be written -->\n <add name=\"xml\" type=\"System.Diagnostics.XmlWriterTraceListener\"\n initializeData=\"e2eTraceTest.xml\" \/>\n <!-- To log to a Console, use this instead of previous Node:\n <add name=\"console\" type=\"System.Diagnostics.ConsoleTraceListener\" \/>\n -->\n <\/listeners>\n <\/source>\n <\/sources>\n <!-- Setting he 'autoflush' attribute to 'true' ensures that the trace\n sources flush to disk after each trace -->\n <trace autoflush=\"true\" \/>\n <\/system.diagnostics>\n<\/configuration>\n<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"Tracking down bugs in distributed systems can be really difficult. One of the technologies we’re using in Indigo to help make this easier is known as “E2E Tracing” (for End to End Tracing). Of course, this technology is only as good as the traces that a system emits. In Beta 1, we weren’t so good […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[],"class_list":["post-89","post","type-post","status-publish","format-standard","hentry","category-indigo"],"_links":{"self":[{"href":"https:\/\/kennyw.com\/index.php?rest_route=\/wp\/v2\/posts\/89","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kennyw.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kennyw.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kennyw.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/kennyw.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=89"}],"version-history":[{"count":0,"href":"https:\/\/kennyw.com\/index.php?rest_route=\/wp\/v2\/posts\/89\/revisions"}],"wp:attachment":[{"href":"https:\/\/kennyw.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=89"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kennyw.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=89"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kennyw.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=89"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}