The latest articles on Forem by Shubham Jindal (@skjindal93). https://forem.com/skjindal93 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F632760%2F7e695629-0cfa-4b62-9098-daa00849f262.jpeg https://forem.com/skjindal93 en Shubham Jindal Mon, 17 May 2021 12:00:21 +0000 https://forem.com/hypertrace/introducing-hypertrace-4k87 https://forem.com/hypertrace/introducing-hypertrace-4k87 <p><a href="https://github.com/hypertrace/hypertrace">Hypertrace</a> is a distributed tracing platform which digests distributed traces from different sources, provides deep observability into your microservices, and slice-and-dices your services, endpoints, traces and attributes.</p> <p>A well loaded definition! And still it doesn't do it justice.</p> <h2> Microservices </h2> <p>Microservices are trendy these days. But the more microservices, the more the burden of managing, monitoring and debugging them. Microservices can be like a spider web, just waiting to tangle you up in its trap.</p> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--l2O_ycjf--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://cdn-images-1.medium.com/max/6996/1%2AkAWXqX663tFvl-JWIcpMlg.png" alt="Monolithic vs Microservices"></th> </tr> </thead> <tbody> <tr> <td> <em>Monolithic vs Microservices</em> Source: <a href="https://devopedia.org/microservices">https://devopedia.org/microservices</a> </td> </tr> </tbody> </table></div> <h2> Distributed Tracing </h2> <p>Distributed Tracing is a way to provide Observability into your services within your microservices architecture.</p> <blockquote> <p>Monitoring tells you whether a system is working, observability lets you ask why it isn't working<br><br> — Baron Schwartz</p> </blockquote> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--W-0J6DlO--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://cdn-images-1.medium.com/max/3624/1%2AgdzvMSWi4NfTQYFi6lNPEw.png" alt="Observability using Distributed Tracing"></th> </tr> </thead> <tbody> <tr> <td><em>Observability using Distributed Tracing</em></td> </tr> </tbody> </table></div> <p>Distributed Tracing tells a story of what's already happened in your system so you can quickly identify your problem and find a solution.<br> <a href="https://zipkin.io/">Zipkin</a> and <a href="https://www.jaegertracing.io/">Jaeger</a> are currently the two most popular distributed tracing systems.</p> <h2> Why Hypertrace? </h2> <p>Hypertrace turns distributed traces into Services, APIs and Backends using a custom pluggable architecture. Any custom logic can be plugged to discover business specific entities with simple configuration changes and surfaces the data to be slice-and-diced, instead of constrained by generic tracing platform features. <br> Hypertrace supports all standard <a href="https://docs.hypertrace.org/instrumentation/">instrumentation</a> libraries and agents. If your application is already instrumented with OpenTelemetry, Jaeger or Zipkin, Hypertrace will work out of the box with your application telemetry data. </p> <p>In addition, Hypertrace provides:</p> <ul> <li>A trace enricher which turns traces into a service dependency graph with endpoints, traces and attributes</li> <li>Flexibility to carefully examine transactions</li> <li>Observability for Services, APIs, and Backends (databases, cloud services, etc.)</li> <li>Metrics and Visibility into Services, APIs, and Backends</li> <li>Root Cause Analysis</li> <li>Identification of Performance Bottlenecks</li> </ul> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--5Pfz_6kH--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://cdn-images-1.medium.com/max/2400/1%2AhSQ9fFsM3Wt4mOWCvN5lWg.png" alt="Slicing and Dicing Transactions"></th> </tr> </thead> <tbody> <tr> <td><em>Slicing and Dicing Transactions</em></td> </tr> </tbody> </table></div> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--6GPkbY4Z--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://cdn-images-1.medium.com/max/2400/1%2AE9lOwH4RW0ys7KgX6NxYMg.png" alt="Distributed Tracing"></th> </tr> </thead> <tbody> <tr> <td><em>Distributed Tracing</em></td> </tr> </tbody> </table></div> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--ND01d9N7--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_66%2Cw_880/https://cdn-images-1.medium.com/max/2400/1%2At2dXn8M-TW4K4qx5U7dq1Q.gif" alt="Services, APIs and Backends"></th> </tr> </thead> <tbody> <tr> <td><em>Services, APIs and Backends</em></td> </tr> </tbody> </table></div> <p>Hypertrace boasts of features like:</p> <ul> <li>P50, P90, P99 metrics (<em>Averages can be misleading</em>)</li> <li>Better data visualizations (<em>Waterfall, Scatter Plot, Area Chart</em>)</li> <li>Wide range of filters, search, sorting, and grouping functionalities</li> <li>Automatic discovery of Services, APIs, and Backends</li> </ul> <p>Hypertrace is for you, if you are looking for the following information:</p> <ul> <li>Traces with duration &gt; 5 seconds</li> <li>Traces with status code as 4xx or 5xx ️</li> <li>Number of calls made to an API</li> <li>APIs within a Service</li> <li>Performance of Services, APIs, and Backends</li> </ul> <p>To learn more, visit <a href="https://docs.hypertrace.org/getting-started/">Hypertrace docs</a> or <a href="https://docs.hypertrace.org/getting-started/">Getting Started with Hypertrace</a>. <br> Do check out Hypertrace on <a href="https://github.com/hypertrace/hypertrace">Github</a> and join Hypertrace community on <a href="https://bit.ly/hypertrace-community-slack">Slack</a></p> cloudnative kubernetes contributorswanted performance