Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

OpenTelemetry

github.com

Post reply on HN
Print view View original

61–66 of 66 posts

Re: OpenTelemetry

#61

Post by brown9-2 »

ahachete wrote: post #6
setheron wrote: post #5

The reference Java implementation uses too much hard-coded static variables. Look sexy for demonstration, but is it configuration nightmare. I had a lot more success and ease of use using open zipkin, highly recommend.

I'm not affiliated with otel, but I'd say it is just otel is still moving forward quickly and there's no good (almost not) documentation on how to use it. I did some small setup with otel, Java and Quarkus, and I will publish a blog post soon on how I did it.

The lack of documentation is a problem, and I’m not sure that moving fast is a great excuse.

OpenCensus has the same problem - some pages have said “coming soon” for years https://opencensus.io/advanced-concepts/context-propagation/

Re: OpenTelemetry

#62

Post by jcchavezs »

candiddevmike wrote: post #4

Here be dragons. I really want to use this project, but the spec and libraries keep changing. I would not adopt this yet, too much is in flux. As an aside, I think this project is suffering from analysis paralysis. Ship a stable 1.0, iterate towards a 2.0 eventually based on user feedback. You aren't going to release a perfect 1.0.

Unfortunately this is what happens when you marketing promises instead of libraries. If CNCF wasn't that eager to market OTel over Opencensus this spec would have evolved naturally but you know, this is business work.

Re: OpenTelemetry

#63

Post by kortex »

maurys wrote: post #49

Just a quick summary. Trace - One unique id for an "action", say customer purchasing an item. A set of spans exist under a trace. Span - An interval with a start time and duration. Can add tags for querying. Can add logs for richer information but not indexed. Each span belongs to exactly one trace. Baggage - key value pairs you can pass between services. They aren't tagged as part of the span or trace, but the recei…

Thank you, these definitions are great. I muddled my way trough the example and had to infer the difference between, trace and span from context.

I still don't get how trances/spans are shared across rpc boundaries but I know that's a thing one can do.

Re: OpenTelemetry

#64

Post by polskibus »

harpratap wrote: post #58
polskibus wrote: post #55

Earlier quoted context omitted.

It would be great if they could all come under common OpenMonitoring umbrella, as ApplicationInsights does it.

Not sure what OpenMonitoring is but OpenTelemetry = Tracing + Metrics + Logging. So we don't really need any more Open-X standards in the observability space IMO

You are right, acc. https://opentelemetry.io/about/

Logging support is incubating.

Re: OpenTelemetry

#65

Post by dkarlovi »

kortex wrote: post #63
maurys wrote: post #49

Just a quick summary. Trace - One unique id for an "action", say customer purchasing an item. A set of spans exist under a trace. Span - An interval with a start time and duration. Can add tags for querying. Can add logs for richer information but not indexed. Each span belongs to exactly one trace. Baggage - key value pairs you can pass between services. They aren't tagged as part of the span or trace, but the recei…

Thank you, these definitions are great. I muddled my way trough the example and had to infer the difference between, trace and span from context. I still don't get how trances/spans are shared across rpc boundaries but I know that's a thing one can do.

As I understand it, you pass your current span ID to the remote RPC endpoint, it continues adding to it from there, creating their own nested spans etc.

When it gets back to you and all spans are merged, you can see the whole picture, but don't need to provide all the details all the way down.

Re: OpenTelemetry

#66

Post by mikewarot »

austinlparker wrote: post #35
systemvoltage wrote: post #34

Earlier quoted context omitted.

The fact that this is the top comment and most people are confused about what Open Telemetry is about should indicate that it is not clear. This is too often a mistake - not knowingly. It's like proof reading, I always think my writing is correct until someone else points out mistakes.

Thanks for the feedback, I just opened a PR to add a link from the spec readme to our website to hopefully guide people to better information.

Before I stopped reading, there was an example of a button being pushed... but there was no actual trace of a button being pushed... just lots of words and descriptions, which killed it for me.

I just want to see what I'm getting into, not a vocabulary or jargon lesson, at least at first.

That would lead us to then wonder why it was done that way, etc... and drive interest.

Post reply on HN