dd-trace-rb
opentelemetry-ruby
| dd-trace-rb | opentelemetry-ruby | |
|---|---|---|
| 5 | 1 | |
| 363 | 526 | |
| 0.6% | 0.8% | |
| 10.0 | 8.5 | |
| 5 days ago | 5 days ago | |
| Ruby | Ruby | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dd-trace-rb
-
Integrating Datadog Instrumented Apps in your OpenTelemetry Stack
This action starts two Ruby on Rails APIs, one instrumented with ddtrace and another with OpenTelemetry SDK, both connecting to an OpenTelemetry Collector that sends data to Jaeger:
-
The end of "Useless Ruby sugar": On intuitions and evolutions
Thing is, once you have 1) and 2), the added complexity of bringing in, integrating, and writing for a different tool to achieve 3) begins to make little sense, when you can just go along and do it just as well in rspec anyway... It's a matter of balance and heavily depends on the project.
> if you're still at Datadog
As a matter of fact I am. Feel free to shoot me an email.
curl -s https://github.com/DataDog/dd-trace-rb/commit/176c642ca73679cabc5fa1a113bc9b600aa04dcd.patch | grep '^From:' -
A few words on Ruby's type annotations state
> For myself, I'm fine with the typing being in a separate .rbs file
We type[0] by having one separate .rbs file per .rb file. Works really well with an editor's vertical splits: type outline on one side, code on the other. That, or use something like vim-projectionist[1].
[0]: (WIP: there's a huge codebase to type, but we're progressively getting there) https://github.com/DataDog/dd-trace-rb/tree/master/sig
[1]: https://github.com/tpope/vim-projectionist
-
Why Authorization Is Hard
Thanks! I'll pass it on to the team :D
I've got to say, the folks at Intercom made it particularly fun. They were sending us traces and graphs from their internal systems when we trying to figure out some issues with them (e.g. we ran into this datadog context problem: https://github.com/DataDog/dd-trace-rb/issues/1389)
opentelemetry-ruby
-
Integrating Datadog Instrumented Apps in your OpenTelemetry Stack
This action starts two Ruby on Rails APIs, one instrumented with ddtrace and another with OpenTelemetry SDK, both connecting to an OpenTelemetry Collector that sends data to Jaeger:
What are some alternatives?
ffi - Ruby FFI
opentelemetry-cpp - The OpenTelemetry C++ Client
contracts.ruby - Contracts for Ruby.
tracetest - 🔭 Tracetest - Build integration and end-to-end tests in minutes, instead of days, using OpenTelemetry and trace-based testing.
inner_performance - Simple database-backed performance monitoring for your Rails app.
opentelemetry-collector-contrib - Contrib repository for the OpenTelemetry Collector