Vendor lock-in is in the small details

• keep

  30 3,292 9.9 TypeScript

  The open-source alert management and AIOps platform (by keephq)

  

  Nope, fully open source - https://github.com/keephq/keep

• SaaSHub

  www.saashub.com featured

  SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

  

• opentelemetry-collector-contrib

  49 2,960 10.0 Go

  Contrib repository for the OpenTelemetry Collector

  

  The article seems to suggest https://github.com/open-telemetry/opentelemetry-collector-co... was silently killed, yet it appears to have been merged in January, am I missing something?

• opentelemetry-collector-co

  13 - -

  The article seems to suggest https://github.com/open-telemetry/opentelemetry-collector-co... was silently killed, yet it appears to have been merged in January, am I missing something?

• micrometer

  5 4,451 9.8 Java

  An application observability facade for the most popular observability tools. Think SLF4J, but for observability.

  

  I've bounced around Splunk, New Relic, Sentry and Datadog over the years. Most recently, I was working with Java and used the open source Vendor-neutral application observability facade Micrometer[1] to test out and confirm which APM we wanted to go with.

  [1] https://micrometer.io

• signoz

  317 18,713 9.9 TypeScript

  SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool

  

  You should also check out SigNoz [1]. It's an open source observability platform with metrics, traces and logs in a single application & based natively on opentelemetry.

  One of the reasons many people use SigNoz is to avoid the vendor lock-in which comes with adding proprietary SDKs of closed source products like DataDog and New Relic in their code.

  If anyone is starting their observability journey today, I think OpenTelemetry is a very good place to start. You can instrument with Otel SDKs and chose a visualization layer/backend which suits your needs best

  (Disclaimer: I am maintainer at SigNoz)

  [1]https://github.com/signoz/signoz

• tracing

  53 5,386 7.1 Rust

  Application level tracing for Rust.

  

  > What's been your biggest issues around ergonomics/amenities for OpenTelemetry?

  I can't speak generally, but in the Rust ecosystem the various crates don't play well together. Here's one example: <https://github.com/tokio-rs/tracing/issues/2648> There are four crates involved (tracing-attributes, tracing-opentelemetry, opentelemetry, and opentelemetry-datadog) and none of them fit properly into any of the others.

• hyperdx

  20 6,606 9.5 TypeScript

  Resolve production issues, fast. An open source observability platform unifying session replays, logs, metrics, traces and errors powered by Clickhouse and OpenTelemetry.

  

  Oh huh! What would you do with span start independent of stops?

  A tangent on logcat - local observability to me is a really intriguing area, I think there's a story of Otel for local as well if someone can build a good enough local DX for consuming them (we've been told a number of times about this https://github.com/hyperdxio/hyperdx/issues/7 as an example)

Suggest a related project