51–60 of 72 posts
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...?
Open Telemetry seems super complex compared to our current setup of Micrometer with Prometheus and Log4j2 with Json output. I wonder if it's worth it to replace both metrics and logging just to take advantage of OT's tracing capability.
Earlier quoted context omitted.
OpenTelemetry allows you to measure performance of your frontend and backend, but it's not a survey tool. DataDog is one of many compatible backends that works with OpenTelemetry, but you can also use Jaeger OSS, Honeycomb, Lightstep, and others.
Strictly only the performance or can it also answer usage questions like: When customers go through this workflow step, they use this option/button 90% of the time and the other options are used rarely?
Anybody has a recommendation on litterature/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.
Anybody has a recommendation on litterature/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.
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. Historicaly APM (application performance monitoring) also owned collection, vendor locked-in and didn’t evolve price per value. Open-source collection standard allows users to choose or switch to the bes…
I love OpenTelemetry, but for Java, I wish adoption would slow down until the implementation catches up. For example, if you visit the OpenCensus site, it tells you on every page that OpenTelemetry is the way to go now. Yet OpenTelemetry's Java metrics implementation is still listed as alpha, and functionality as basic as tags didn't work when I last tried it. Or, I've been working with Datadog lately, and I want to…
Only complaint is the churn over the past year, especially in the metrics world. We use OTel Python and have had to pin our libraries to an older version so we can continue to record metrics stably until the python SDK catches up to the latest metrics specification.
I see a telescope. Is it space related? Telemetry of satellites?
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.
Earlier quoted context omitted.
The developer of the web app... who is already running all sorts of other code in your browser.
Sure. Like any JavaScript. As long as the provider of the service is transparent about what is collected, what’s the problem? There’s nothing preventing a system provider from making this collection opt-in. What’s with the assumption that the service provider cannot observe how their system performs?
In a similar way, your software is borrowing time and computing resources from your users. You need to use them sparingly and respect that you do not own their hardware, but are a guest they have invited in. It's not your computer to do whatever you want with.