Overview
For this tutorial, you will be starting with an uninstrumented distributed sample app. Uninstrumented means, that this app will initially not have any code, that will emit telemetry, such as traces, metrics and logs.
You will add the OpenTelemetry SDK to that application, and afterwards instrument the application by adding traces, metrics and logs. You will do that, for your dependencies and for your custom code.
When you have successfully instrumented the app, you will learn how to export your telemetry to the console and then using OTLP to the OpenTelemetry collector. You will see how you can receive telemetry with the collector, process that telemetry and eventually export it to a backend, that can visualize your data.
Finally, you will learn how OpenTelemetry can correlate telemetry across service boundaries, and how you can add more context, like service, container or host information to your telemetry.
By the end of the tutorial, you will have learned how to instrument your own app using OpenTelemetry.
Start by setting up the sample application that will be used throughout the tutorial.
Note
You can follow the tutorial using your own application as well, but we recommend that you use the provided sample application when you go through it for the first time, such that you have an easier time when you need to troubleshoot or go back some steps.Feedback
Was this page helpful?
Thank you. Your feedback is appreciated!
Please let us know how we can improve this page. Your feedback is appreciated!