41–50 of 72 posts
How does this relate to OpenMetrics, if at all?
[0] https://github.com/open-telemetry/opentelemetry-specificatio...
Hello, Hacker News! https://share.getcloudapp.com/4guP9P6p (stats gathered from opentelemetry-js)
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. 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 thi…
I didn't think to much on this but I played with it once in a hackathon and made a tool that showed how one customer site performed versus another customer site by showing performance comparisons on workflow spans and augmenting this information with metrics of most used tools to get an indication if the other site was maybe faster because it used different parts of the product to perform certain actions faster.
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
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. Seve…
Earlier quoted context omitted.
> "they" who are receiving the data being collected about the user I'm curious why you automatically assume data is being collected about the user ? OpenTelemetry is about Observability, not user tracking.
If you're collecting data from software running on someone's device, that's someone else's user data. I think the term of art is metadata. In some ways, such information is just as important as biometrics and passwords and pii. Deanonymizing becomes possible when metadata is cross-referenced. Metadata should be subject to as strict protection and consent rules as documents, health info, or any other "obvious" private…
Earlier quoted context omitted.
If you're collecting data from software running on someone's device, that's someone else's user data. I think the term of art is metadata. In some ways, such information is just as important as biometrics and passwords and pii. Deanonymizing becomes possible when metadata is cross-referenced. Metadata should be subject to as strict protection and consent rules as documents, health info, or any other "obvious" private…
NOFI, just to understand if we talk the same thing here, you mean to say that a trace that traces the time it took the product you use to do a query that goes through three different backend services is private data that is owned by you and can only be collected by your consent. Not so much because you are against collecting that information, you may very well accept it to be collected, but because technically the da…
I understand it seems extreme, but it's really not.
Any data generated by or on a user's device is private data. Recording that data is surveillance. No matter how harmless it might seem, data collection should be consensual, transparent, and ephemeral. You should specify, explain, and obtain consent for any and every variable. Anything you do with the data should be reportable to the user. Anything less creates opportunities for abuse.
Logging ip address connections is a great example. It's simple and trivial but how many RIAA piracy lawsuits do we have to see inflicted on innocents before we decide keeping those logs might not be a great idea?
The misuse of metadata by law enforcement through plausible narrative crafting is ubiquitous. It's not about the developer's intentions, it's about collection of surveillance records that can be seized or stolen and weaponized.
I wonder if it's worth it to replace both metrics and logging just to take advantage of OT's tracing capability.
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.
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.
A key benefit you might not be getting that OpenTelemetry (and Fluentd for logs in the interim) provides is routing. The ability to trial multiple downstream storage solutions is useful!