OpenTelemetry Collector, Deployment Methods & Production Ready | The OpenTelemetry Bootcamp

Learn how to use OpenTelemetry to get full-stack observability of your distributed system.
The OpenTelemetry Bootcamp brings you a weekly video series of everything you need to get started with OpenTelemetry. From zero to hero, this is where you get your OpenTelemetry questions answered.
In this episode, we're taking a deep dive into the OpenTelemetry Collector, including setting up receivers, processors, and exporters. We also covered how to set up a database and how to create a production-ready environment.
🔗 A short guide covering the OpenTelemetry basics: www.aspecto.io/blog/what-is-o...
🔗 Watch more Bootcamp episodes here: www.aspecto.io/opentelemetry-...
🔗 Join the Bootcamp's channel on the CNCF Slack to keep the conversation going: cloud-native.slack.com/messag...
Link to the source code: github.com/aspecto-io/opentel...
--
🎉 The OpenTelemetry Bootcamp Episode 3! 🎉
💻 In this episode:
✅ Deploying a collector
✅ Setting up a database
✅ Implementation & production-ready deployment
--
📆 Upcoming Bootcamp video schedule: www.aspecto.io/opentelemetry-...
--
#opentelemetry #opentelemetrybasics #cncf #opentelemetryarchitecture #cloudnative #distributedtracing #microservices #observability #collector
--
0:00 - Intro
2:26 - What to expect
5:20 - The OpenTelemetry collector
7:49 - Architecture overview option #1
9:20 - Option #1 pros and cons
9:48 - Architecture overview option #2
12:25 - Option #2 pros and cons
13:37 - Our desired architecture
16:25 - OpenTelemetry collector setup: receivers
20:40 - OpenTelemetry collector setup: processors
23:26 - Q: Processor limitations
24:59 - OpenTelemetry collector setup: processors
26:25 - OpenTelemetry collector setup: exporter
36:28 - Mid-session summary
38:09 - Setting up the OpenTelemetry collector agent
44:46 - Adding Elasticsearch
49:15 - General recommendations for production deployment
50:18 - Wrapping up
51:16 - Q&A
52:42 - Updating from OpenTracing to OpenTelemetry
55:17 - How to measure my traffic
57:22 - Outro

[@shephaligupta5956]

This full series is absolutely great for someone to start from scratch! Thanks for putting this together :)

[@jo.joseph]

Beautifully explained🤓

[@aspecto_io]

Thank you so much!

[@heyitspranav]

Hi, these bootcamps videos are awesome. I have a question - could you point me to the documentation where I can find all the possible configuration settings of otel collector? Thanks

[@aspecto_io]

I believe this should help opentelemetry.io/docs/collector/configuration/ - Happy to answer more questions if you have any :)

[@drich188]

took a bit to work through the demo, but another excellent video. The density is of real value. Thanks for posting the GitHub link

[@cramhead]

I thought that one of the important architectural characteristics of Prometheus is that it collects data from the services that it monitors. By having the Prometheus exporter is it providing a new location to scrape or is it pushing data to Prometheus?

[@cramhead]

Michael you totally answered the question, i..e. Prometheus collects it from the OTEL-collector. Thanks for being so through

[@pennpeng1750]

I have a naive question about that why you need to use a col-agent and a col-gateway? I mean it's ok to use only one otel-collector to receive, process, and then export the span data to jaeger-collecor then store into ES? Meanwhile, another question is that in your scenario, if the jaeger-agent component is unnecessary because your endpoint is "jaeger:14250" which means your directly connect to jaeger-collector?

[@aspecto_io]

Hi! so for the first question, you can use a single collector, there is nothing wrong with that.
Yes, you don't have to user the jaeger-agent you can work directly with the collector

[@martinp3839]

Excellent. Please post link to the source code if possible.

[@aspecto_io]

Sure thing! have a look here - github.com/aspecto-io/opentelemetry-bootcamp

[@martinp3839]

@@aspecto_io Appreciate it.