OpenTelemetry
opentelemetry.io
OpenTelemetry
1–10 of 72 posts
Re: OpenTelemetry
#2I hate that this specification and most of the other ones use spans that have a beginning and end rather than events that start and end the span. What if it crashes before it sends out the span? What if it is taking a very long time to complete?
Re: OpenTelemetry
#3I hate that this specification and most of the other ones use spans that have a beginning and end rather than events that start and end the span. What if it crashes before it sends out the span? What if it is taking a very long time to complete?
Data query wise it's significantly more complicated to compile 2 db row spans than it is to do queries on one db row spans. The library that makes and manages those spans before uploading can deal with those use cases internally if it wants, a lot of these systems have support for single point events too.
Re: OpenTelemetry
#4I hate that this specification and most of the other ones use spans that have a beginning and end rather than events that start and end the span. What if it crashes before it sends out the span? What if it is taking a very long time to complete?
For the long running scenario, why not use Links? The specification describes[1] a similar scenario and how links can be leveraged to causally relate spans even across trace boundaries.
As for the crashing scenario, this seems like an application-level concern. Ideally it is not waiting until the crash to send traces. Depending on the environment, the application could handle the crash and deliver the telemetry leading up to it before shutting down.
[1]: https://github.com/open-telemetry/opentelemetry-specificatio...
Re: OpenTelemetry
#5Not a mention of "opt-in only, because we respect privacy"...
Please stop helping spy on users! Be the change you want to see in the world!
Re: OpenTelemetry
#6Not a mention of "opt-in only, because we respect privacy"... Please stop helping spy on users! Be the change you want to see in the world!
That's because this tool has nothing to do with "spying on users".
It's a set of tools and a specification for instrumenting applications and collecting logs/metrics/traces from them. It's used to ask questions like "why is this page slow to load?" and get answers like "because it talks to the billing microservice which has a really slow SQL query".
This isn't the same sort of telemetry that desktop software vendors collect.
Re: OpenTelemetry
#7I really hope we’ll have an open standard for tracing. Right now the common solutions are vendor-locking and can’t be integrated in OSS projects
Re: OpenTelemetry
#8I really hope we’ll have an open standard for tracing. Right now the common solutions are vendor-locking and can’t be integrated in OSS projects
Open tracing works just fine.
Re: OpenTelemetry
#9We are trying to get a better understanding of how customers use our desktop application. We are urged by management to use Qualtrics, but it feels like it is not the right tool for the job.
How would you say does opentelemetry compare to Qualtrics?
Is Qualtrics a tool where users need to actively fill out surveys and opentelemetry collects passively user interactions?
There is also other names floating around in this space like DataDog or OpsTrace, where I am not clear how to place them.
Re: OpenTelemetry
#10I really hope we’ll have an open standard for tracing. Right now the common solutions are vendor-locking and can’t be integrated in OSS projects
That's definitely a goal of OTel! And it seems to be working. Anecdotally, OTel support has been very important for my workplace (we sell observability tooling https://www.honeycomb.io/) in terms of prospects. I think a lot of decision makers at companies are realizing that they can't afford not to have vendor-neutral instrumentation.
And tracing is GA in most SDKs as well, so you should feel ready to adopt it. Several vendors and OSS tools support it (or you can export your data to another format with the OTel Collector).