Hacker GitHub

← All repos

open-telemetry/opentelemetry-collector-contrib

View on GitHub ↗ ★ 5,034 Go

Contrib repository for the OpenTelemetry Collector

33 mentions on Hacker News by 28 people: 1 story, 32 comments · first 2021-09-02 · latest 2026-10-19

Mentions per year 33 mentions · busiest year 2023 (18)
20082026
  1. If you are using a Datadog, Langfuse, Langchain, or other OTEL target, you do nothing. Just query it. Build alerts, dashboards, and datasets; whatever you normally do with your OTEL collector. A forward OTEL collector deployment is still…
  2. And the receiver: https://github.com/open-telemetry/opentelemetry-collector-co... I'll have to try this! edit: actually Jaeger can just read those files directly, so no need to run a collector with the receiver. This is great!
  3. https://github.com/open-telemetry/opentelemetry-collector-co...
  4. Great questions! OTel Metrics: I get it, it's specified as almost a superset of everyone's favorite metric standards with config for push/pull, monotonic vs delta, exponential/"native" histograms, etc. I have my preferences as well which…
  5. To be fair, the setup of the article works with most modern observability solutions, in same cases just by replacing the endpoint and authentication token. Turning telemetry processing into a sort of utility is one of the great things that…
  6. > having a decent way to get metrics from logs ad-hoc completely solves the metric cardinality explosion. last i checked, the span metrics connector[1] was supposed to "solve" this in otel; but i'm not particularly inclined, as…
    comment by thewisenerd · 2025-04-25 · in Observability 2.0 and the Database for It
  7. imo Datadog is pretty hostile to OTel too. Ever since https://github.com/open-telemetry/opentelemetry-collector-co... was nearly killed by them I never felt like they fully supported the standard (perhaps for good reasons) OTel is a bear…
  8. > - Helm sucks, but so does Kustomize Helm != Kubernetes, FWIW I'd argue that Kustomize is the bee's knees but editor support for it sucks (or, I'd also accept that the docs suck, and/or are missing a bazillion examples so us mere mortals…
    comment by mdaniel · 2024-11-27 · in Dear friend, you have built a Kubernetes
  9. yes! the full stack includes our recommended schema which has the indexes set up - it's a drop in replacement for anything that would ingest Otel-based telemetry! If you already have Promtail setup - you might want to set up a collector or…
  10. Yes, in the collector-contrib repository you already had support for traces https://github.com/open-telemetry/opentelemetry-collector-co...
    comment by coffeeandhn · 2024-06-18 · in Translate Datadog Metrics into OTLP
  11. multiple services, that should be sampled based on latency. this only works if you have something like: https://github.com/open-telemetry/opentelemetry-collector-co... or https://grafana.com/docs/tempo/latest/configuration/grafana-... in…
    comment by merb · 2024-06-17 · in The problem with OpenTelemetry
  12. you can add https://github.com/open-telemetry/opentelemetry-collector-co... at signoz's otel-collector which will scrape your service's endpoint periodically. If your service is down, this will give 5xx error and you can set an alert on…
  13. The open telemetry collector does just that. https://github.com/open-telemetry/opentelemetry-collector-co...
  14. Thanks for the reply. Would the Spotlight sidecar possibly be able to run independently and consume spans emitted by the Sentry exporter[0] or some other similar flow beyond strictly exporting directly from the Sentry SDK provided by…
    comment by conor- · 2023-12-06 · in Spotlight: Sentry for Development
  15. If you are using the prometheus exporter, you can use the transform processor to get specific resource attributes into metric labels. With the advantage that you get only the specific attributes you want, thus avoiding a cardinality…
    comment by ronyaurora · 2023-11-21 · in Migrating to OpenTelemetry
  16. 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?
    comment by Volundr · 2023-10-31 · in Vendor lock-in in the observability space
  17. OpenTelemetry is a large suite of software, that supports many use cases. I think you got what you wanted but didn't realise it! The dedicated executable that you are after is called the OpenTelemtry Collector. The OpenTelemetry SDK for…
    comment by d8c6c050cb0a4d7 · 2023-10-23 · in Ask HN: What's Your Opinion on Opentelemetry?
  18. This arch is how the big players do it at scale (ie. datadog, new relic - the second it passes their edge it lands in a kafka cluster). Also otel components lack rate limiting(1) meaning its super easy to overload your backend storage…
  19. I really like this idea. And there is an OTEL exporter to AWS S3, still in alpha but I'm gonna test it soon: https://github.com/open-telemetry/opentelemetry-collector-co...
  20. Just install opentelemetry libs. I found this example with a quick search: https://dev.to/grunet/leveraging-opentelemetry-in-deno-45bj opentelemetry has a service you can run that will collect the telemetry data and you can export it to…
    comment by curioussavage · 2023-09-20 · in Tracing: Structured logging, but better
  21. Ah yeah the easiest way is probably using the OpenTelemetry collector to set up a process to pull your logs out of jounrnald and send them via otel logs to HyperDX (or anywhere else that speaks otel) - the docs might be a bit tricky to go…
  22. …that mess into their head may ask 'err, what's the difference between go.opentelemetry.io/collector and github.com/open-telemetry/opentelemetry-collector-contrib?' $ curl -fsS go.opentelemetry.io/collector | grep go-import <meta…
    comment by mdaniel · 2023-06-22 · in Go 1.21 Release Candidate
  23. Apparently OT is a threat to DD to the point of them asking contributors to not add support for their agents… https://github.com/open-telemetry/opentelemetry-collector-co...
  24. Good news! The PR is moving again! https://github.com/open-telemetry/opentelemetry-collector-co...
  25. The OP didn't link directly to the comment and it's buried in the thread: https://github.com/open-telemetry/opentelemetry-collector-co...
  26. https://github.com/open-telemetry/opentelemetry-collector-co...
  27. And then went back uphill in https://github.com/open-telemetry/opentelemetry-collector-co...
  28. Here is where it started to go downhill: https://github.com/open-telemetry/opentelemetry-collector-co...
  29. Link to exact comment: https://github.com/open-telemetry/opentelemetry-collector-co...
  30. ▲ 349
    DataDog asked OpenTelemetry contributor to kill pull request
    story by raybb · 2023-01-26 · 95 comments
  31. What schema does SigNoz use with Clickhouse? The Open Telemetry Collector uses this schema https://github.com/open-telemetry/opentelemetry-collector-co... and I found out that accesing map attributes is much slower (10-50x) compared to…
  32. Uptrace / Go process will buffer spans in memory for some short period of time (5-15 seconds). It does not work for long traces, but most traces are short. There is some discussion at https://github.com/open-telemetry/opentelemetry-collecto…
  33. Podman does support docker API so you can use something like the OpenTelemetry Collector to fetch metrics using the docker API and forward them to prometheus. Collector: https://github.com/open-telemetry/opentelemetry-collector-co...…