OpenTelemetry

I love OpenTelemetry, but for Java, I wish adoption would slow down until the implementation catches up.<p>For example, if you visit the OpenCensus site, it tells you on every page that OpenTelemetry is the way to go now. Yet OpenTelemetry&#x27;s Java metrics implementation is still listed as alpha, and functionality as basic as tags didn&#x27;t work when I last tried it.<p>Or, I&#x27;ve been working with Datadog lately, and I want to add dynamic span metadata. My options appear to be either to wire up the (deprecated) OpenTracing client, or set up a full collector&#x2F;agent suite of OpenTelemetry processes (whose default tutorial configurations appear to be invalid in places).<p>worth I guess, but bumpier than I&#x27;d like.

I belive OpenTelemetry will make distributed tracing mainstream. Traces are the best tool to debug problems, yet as their are expensive (both in dev work and license) to implement they are way less popular than logs.<p>Historicaly APM (application performance monitoring) also owned collection, vendor locked-in and didn’t evolve price per value.<p>Open-source collection standard allows users to choose or switch to the best vendor.<p>Personally, I recommend Sumo Logic (disclaimer: I work there). We have rich full-text query capabilities on spans with parsing and aggreagations on query time…

Hello, Hacker News! <a href="https:&#x2F;&#x2F;share.getcloudapp.com&#x2F;4guP9P6p" rel="nofollow">https:&#x2F;&#x2F;share.getcloudapp.com&#x2F;4guP9P6p</a> (stats gathered from opentelemetry-js)

I 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?

Open Telemetry seems super complex compared to our current setup of Micrometer with Prometheus and Log4j2 with Json output.<p>I wonder if it&#x27;s worth it to replace both metrics and logging just to take advantage of OT&#x27;s tracing capability.

We 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.<p>How would you say does opentelemetry compare to Qualtrics?<p>Is Qualtrics a tool where users need to actively fill out surveys and opentelemetry collects passively user interactions?<p>There is also other names floating around in this space like DataDog or OpsTrace, where I am not clear how to place them.

Anybody has a recommendation on litterature&#x2F;blogs addressing the subject of observability? I’m contemplating an SRE job offer and although I have my share of knowledge, I am still out of my league whenever I glance at the cncf map in the observability category. I feel that the field has exploded with new components and new ways, and I’m sometimes afraid of taking the wrong path.

As someone not familiar with this project, and looking at the landing page, I have no idea what this does. I understand it has something to do with telemetry, but for what? And what would it help me with? How would I use it.<p>I see a telescope. Is it space related? Telemetry of satellites?<p>Just my two cents as someone not familiar with the project, and has no idea how to use it or how it would solve a problem I have.

Forgive me for having no idea what this project is, but is this a telemetry library for web infrastructure, or is this an open source telemetry library for monitoring high frequency signals from hardware devices, or...?

It is nice that the proto files are unambiguous that trace time is represented as unix epoch nanos, and it is declared `fixed64` the way Jesus intended, but it&#x27;s too bad the specification made it to 1.0 without simply mandating that timestamps are always in unix epoch nanos. Having uncertainty about the precision of timestamps has caused and will continue to cause loads of bugs. If there is some language platform out there that can&#x27;t figure out the time in nanos, that language platform should simply be ignored.

How does this relate to OpenMetrics, if at all?

I 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

Not a mention of &quot;opt-in only, because we respect privacy&quot;...<p>Please stop helping spy on users! Be the change you want to see in the world!