Hey guys, if you're ready to get started, you can head over to this tutorial. There, I'll show you how to instrument your code, including some really useful tricks the pros use: ua-cam.com/video/a1qWMzpDuI4/v-deo.html
Thanks Henrik, I really enjoy the way you explain things. They are very well structured and helped me gained a better understanding about OpenTelemetry as a whole. Keep up the good work!
it would be great to give a solid example on 'why' would anyone need the OpenTelemetry. Video jumps into details quite quickly but it is not clear why would someone need to bother with OT
Hi , I usually look at each language listend in :opentelemetry.io/docs/instrumentation/ ( there is a small table showing the current level of stability for traces, metrics and logs)
Is it able to add some attributes to metric counter like for example service_name, group_name? Based on API we can simpy add attribute in function Add(value, attrib), but once I capture the data I only see Metrics structure (name , description, unit,kind) that you mention in movie. I dont see any attributes. I also add this in config: processors: attributes: actions: - key: "attr_name" action: "insert" from_attribute: "attr_name"
For this i would recommend to use the Transform procesor with the new OpenTelemetry Transformation language. you will be able to adjust the metric and the datapoint.
Hi, OpenTelemetry Logs is not fully implemented. We should have it in few month. therefore you will need to rely on Fluentd or fluentbit to collect, parse your logs. BTW fluentbit v2 supports logs, metrics and soon traces. Are you trying to instrument your application using OpenTelemetry?
Most of the time it's really hard to understand what you're saying. Your talking goes from Veeerrrrryyyy slloooooww.... to... vyaxtrmlfst. Not everyone is a native speaker, not everyone uses the same terms and so not everyone can guess what you just said. F.E. 7:10 -> A trace. what is a trace ? A trace is ..... debltrcldown..... we all know that" Ok, i THOUGHT i knew what a trace is, but i absolutely can NOT decypher what word - or words - you've been using there. Now imagine someone who does NOT know - or is unsure about - what a trace is. First - you DID deliver an explaination. an explaination nobody can understand. And you ended it with "we all know that" making that person feel even worse since - they DONT know it. Well, maybe they DO know but they dont understand the word there and now they really think they dont know. there are a LOT of spots in the video where the speed changes from "come on! get the sentence going! dont try to be so 'overly dramatic' about what you're going to say!" to rightdown "you should have become a rapper"
Hey guys, if you're ready to get started, you can head over to this tutorial. There, I'll show you how to instrument your code, including some really useful tricks the pros use: ua-cam.com/video/a1qWMzpDuI4/v-deo.html
Thanks Henrik, I really enjoy the way you explain things. They are very well structured and helped me gained a better understanding about OpenTelemetry as a whole. Keep up the good work!
Thank you for this video! This is exactly what I needed to understand OTel!
You're so welcome!
Great presentation. It was covering majority of the topics at very high level.
Excellet pronuntiation, pause and knowledge about o11y
Thanks for short and detailed explanation!
You're welcome!
Your voice is incredible.
great video, thank you very much.
it would be great to give a solid example on 'why' would anyone need the OpenTelemetry. Video jumps into details quite quickly but it is not clear why would someone need to bother with OT
Good point. thx for the feedback
Thank you for an awesome introduction to OpenTelemetry.
Where's the stability table shown in component section shared on the website?
Hi , I usually look at each language listend in :opentelemetry.io/docs/instrumentation/ ( there is a small table showing the current level of stability for traces, metrics and logs)
Great content! for a moment I thought Charlie Hunnam was the host :D
yeah it could make sense to create the son of observability ;D
Is it able to add some attributes to metric counter like for example service_name, group_name? Based on API we can simpy add attribute in function Add(value, attrib), but once I capture the data I only see Metrics structure (name , description, unit,kind) that you mention in movie. I dont see any attributes. I also add this in config:
processors:
attributes:
actions:
- key: "attr_name"
action: "insert"
from_attribute: "attr_name"
For this i would recommend to use the Transform procesor with the new OpenTelemetry Transformation language. you will be able to adjust the metric and the datapoint.
How different OpenTelemetry is from AppDynamics(APM) and which is better?
do we still need the fluentd with this opentelemetry components?
Hi, OpenTelemetry Logs is not fully implemented. We should have it in few month. therefore you will need to rely on Fluentd or fluentbit to collect, parse your logs. BTW fluentbit v2 supports logs, metrics and soon traces.
Are you trying to instrument your application using OpenTelemetry?
wow thanks
nice video
Thanks
OpenTelemtry 4:30
Thanks...another issue related to my big fingers :D
1.5x play speed.😊
HELP
You could have been a great lector if you weren't freestyling.
Most of the time it's really hard to understand what you're saying. Your talking goes from Veeerrrrryyyy slloooooww.... to... vyaxtrmlfst.
Not everyone is a native speaker, not everyone uses the same terms and so not everyone can guess what you just said.
F.E. 7:10 -> A trace. what is a trace ? A trace is ..... debltrcldown..... we all know that"
Ok, i THOUGHT i knew what a trace is, but i absolutely can NOT decypher what word - or words - you've been using there.
Now imagine someone who does NOT know - or is unsure about - what a trace is. First - you DID deliver an explaination. an explaination nobody can understand. And you ended it with "we all know that" making that person feel even worse since - they DONT know it. Well, maybe they DO know but they dont understand the word there and now they really think they dont know.
there are a LOT of spots in the video where the speed changes from "come on! get the sentence going! dont try to be so 'overly dramatic' about what you're going to say!" to rightdown "you should have become a rapper"