3 ms·

It's an interesting move given that OTel is not stable yet. :o

hobofan 5y ago
And why exactly is that interesting? Tech companies often use new products before they are stable, how else would they become battle-tested? On the website it even says: "OpenTelemetry is in beta across several languages and is suitable for use. We anticipate general availability soon."
- jonatan-ivanov 5y ago
  I guess because you might not want to go to prod with something on GH scale that is not stable and still subject to have breaking changes? Fyi: that quote has been there for a while.
  - hobofan 5y ago
    It's usually the opposite: You might not want to go to prod with something like this on an SMB scale where you have little resources to navigate tech debt. On a Github scale where you have more engineers available, it's often worth it to adopt cutting-edge alpha/beta software for their novel features, as you generally also have more expertise/mechanisms to ensure stability of the overall product and run less risk of being suffocated in tech debt.
kortex 5y ago
Why is this controversial? OT is great but it's not totally production ready imho. I tried integrating it last year in Python and had almost weekly breaking changes to the internal API calls. I mean, it was a 0.x, so they were well within their liberty, also they don't owe me anything. But it was a bit of a false start for me. Finally they released a 1.0 and the interfaces are more stable, but the docs are still incomplete or stale in some places. I currently use it in a minor way. Frankly I can't wait because I love the tools and ecosystem, but I personally would be hesitant to put it into full blown production at such a big company.
drewbug01 5y ago
One of our goals with early adoption is to contribute back the things needed to make it stable, performant, and useful for everyone. It might make things more difficult for us at times, but we feel we can manage the burden. It’s obviously not our only goal, but we are in a position to help make the system better for everyone and sincerely wish to do so.

And why exactly is that interesting? Tech companies often use new products before they are stable, how else would they become battle-tested? On the website it even says: "OpenTelemetry is in beta across several languages and is suitable for use. We anticipate general availability soon."

jonatan-ivanov 5y ago
I guess because you might not want to go to prod with something on GH scale that is not stable and still subject to have breaking changes? Fyi: that quote has been there for a while.
- hobofan 5y ago
  It's usually the opposite: You might not want to go to prod with something like this on an SMB scale where you have little resources to navigate tech debt. On a Github scale where you have more engineers available, it's often worth it to adopt cutting-edge alpha/beta software for their novel features, as you generally also have more expertise/mechanisms to ensure stability of the overall product and run less risk of being suffocated in tech debt.

kortex 5y ago

Why is this controversial? OT is great but it's not totally production ready imho. I tried integrating it last year in Python and had almost weekly breaking changes to the internal API calls. I mean, it was a 0.x, so they were well within their liberty, also they don't owe me anything. But it was a bit of a false start for me. Finally they released a 1.0 and the interfaces are more stable, but the docs are still incomplete or stale in some places. I currently use it in a minor way. Frankly I can't wait because I love the tools and ecosystem, but I personally would be hesitant to put it into full blown production at such a big company.

drewbug01 5y ago

One of our goals with early adoption is to contribute back the things needed to make it stable, performant, and useful for everyone. It might make things more difficult for us at times, but we feel we can manage the burden. It’s obviously not our only goal, but we are in a position to help make the system better for everyone and sincerely wish to do so.