signoz VS opentelemetry-js

Give https://github.com/SigNoz/signoz a look

Sure, we will include dynatrace and elastic in our next update. The line items are mostly based on how the product does the billing u/RabidWolfAlpha. Datadog has an SKU-based billing structure. If you visit their pricing page, they list down a lot of products, and they bill each of them separately. For example, APM and infrastructure monitoring are two separate paid products. SigNoz is based on usage-based pricing; only pay for how much data you ingest. Billing is based on how much logs, metrics and traces you ingest. There is no separate billing for APM and infrastructure monitoring. SigNoz has most features that Datadog provides, except things like network monitoring, Cloud SIEM, etc. Are you looking for any specific feature? p.s SigNoz is also open source: our github repo.

We are building OpenSource Observability at SigNoz. Have a look at https://github.com/SigNoz/signoz

SigNoz? https://github.com/SigNoz/signoz

Folks on this thread might want to check out SigNoz (https://github.com/SigNoz/signoz). It's an open source alternative to Datadog.

I am one of the maintainers at SigNoz. We have come across many more horror stories around Datadog billing while interacting with our users.

We recently did a deep dive on pricing, and found some interesting insights on how it is priced compared to other products.

Datadog's billing has two key issues:

I am not sure when you tried OpenTelemetry, but it is decently mature now, esp. for tracing. I am a maintainer at SigNoz (https://github.com/signoz/signoz) and we have good support for tracing using Otel for most of the common frameworks.

I agree it was a bit rapidly evolving in early days, but now its much more mature.

You can check out our docs for distributed tracing here - https://signoz.io/docs/instrumentation/

We are building SigNoz (https://github.com/SigNoz/signoz) - an open source alternative to DataDog. We are natively based on opentelemetry and see lots of our users very interested in that.

As mentioned in some other places in the thread, DataDog pricing is very unpredictable and high - and I think more open standards based solutions are the way forward which provides users more predictability and flexibility

You should check out SigNoz (https://github.com/SigNoz/signoz) - It's an open source alternative to DataDog with metrics, traces and logs in a single application. You can just self host it yourself or try the hosted version.

PS: I am one of the maintainers at SigNoz

There's also Signoz (https://signoz.io) a YC-backed company but open source with (recently) paid hosted.

Can it be integrated with Grafana Faro or OpenTelemetry?

4. Register automatic instrumentations. For example, you can automatically trace all XHR requests, fetch requests, page loads, and user interactions. With distributed tracing, you should always prefer automatic instrumentation whenever possible to reduce maintenance and leverage existing conventions. The document load instrumentation allows you to treat the server as the parent span to a given page load, from which the client will then be the root span to everything in the server. This is an extremely powerful concept that allows traces to viewed from the perspective of the user, encapsulating all requests and user interactions in a single trace with no manual instrumentation!

We also trialed Sentry's APM tool (also marketed as a distributed tracing tool). While it had pretty charts, dashboards, niceties like core web vitals, and integrated well with Sentry's error product, its utility as a distributed tracing tool is significantly less powerful than tools like Honeycomb. You will end up using a large amount of your user's bandwidth sending telemetry data that can't fully be leveraged in the Sentry UI. When I last used (in April 2021), the spans of a given trace could only be viewed in a specific part the UI and they couldn't be searched for in queries or used in charts. I'm unsure if this has been updated. But this is not the worse part. Because Sentry uses its own data model for traces, it is not compatible with open source standards such as OpenTelemetry or OpenTracing! The sales team will not tell you this during the trial. This means our entire backend, which was already instrumented with OpenTracing, would now also need to instrument Sentry's tracing (...if they supported the language) in order to connect frontend traces to backend traces. Each team I met with their sales team, I said the same thing: support OpenTelemetry, otherwise you are asking for us to further isolate our backend and frontend teams.

It looks like they have heard this opinion, as they have recently published a blog post about the evolution of the distributed tracing API, citing incompatibility with OpenTelemetry due to their data model. It will require a very large change for them to support this. Meanwhile, OpenTelemetry can be used with any tracing vendor, a large number of languages, the other major instrumentation standards (OpenTracing, OpenCensus), and any trace propagation format.

- [1]: https://github.com/open-telemetry/opentelemetry-js

Consumer lag will quickly show any functional or technical issue with your event stream. By using the code examples from this blogpost, you can avoid having to dive into the SDKs yourself. Of course, you can adopt the metric collection to send the metric to the logs or to another metrics system like prometheus, datadog, or open telemetry.

I would work on getting Open Telemetry pointed at an “all-in-one” Jaegar instance and move on from there: https://www.jaegertracing.io/docs/1.25/getting-started/ https://github.com/open-telemetry/opentelemetry-js Various cloud providers may have a way to collect/view traces as well, but, Jaegar and the Open Telemetry Collector are the open source way to do that. The projects are in the process of converging in some ways — everything is in flux.

OpenTelemetry is a collection of open source tools, APIs, and SDKs for instrumenting, generating, and exporting telemetry data from running software. It provides language-specific implementations for most popular programming languages, including both browser JavaScript and Node.js.

Compatible with SDK v0.24.0

If you are writing a new instrumentation library, observing the tracing output in a UI can be much easier than browsing through textual logs. You can browse the JS instrumentation package for more info and examples.

SigNoz supports OpenTelemetry as the primary way for users to instrument their application. OpenTelemetry is a single, vendor-agnostic instrumentation library per language with support for both automatic and manual instrumentation. You don't need to worry about instrumentation in this tutorial. OpenTelemetry comes with all currently available instrumentation.

OpenTelemetry is a CNCF project, which, among other things, enables the collection of distributed traces.