aniel Schierbeck' via Ruby on Rails:
>> Core wrote:
>>
>>> First PR is up: https://github.com/rails/rails/pull/34305
>>> <https://github.com/rails/rails/pull/34305>
>>>
>>> On Tue, Oct 23, 2018 at 4:33 AM Jeremy Daer
>>>
First PR is up: https://github.com/rails/rails/pull/34305
On Tue, Oct 23, 2018 at 4:33 AM Jeremy Daer wrote:
> On Mon, Oct 22, 2018 at 9:56 AM 'Daniel Schierbeck' via Ruby on Rails:
> Core wrote:
>
>> On Fri, Oct 19, 2018 at 10:15 PM Daniel Azuma wrote:
&g
On Fri, Oct 19, 2018 at 10:15 PM Daniel Azuma wrote:
> Hi folks,
>
> Thought I'd jump in here as the engineer who has done most of the
> implementation on the opencensus gem so far. Ruby support in OpenCensus is
> currently a bit behind other languages—we don't yet have support for stats,
> z-pag
On Thu, Oct 18, 2018 at 9:24 PM Jeremy Daer wrote:
> On Thu, Oct 18, 2018 at 2:52 AM 'Daniel Schierbeck' via Ruby on Rails:
> Core wrote:
>
>> Looks like OpenCensus already has support for development mode UIs,
>> currently only for Java and Go though:
>>
e doing at Zendesk, where you're headed, and
>> whether this sketch aligns well. And anyone else who's working in this area!
>>
>
> We're currently all-in on Datadog, and I've helped improve their
> instrumentation. However, I keep running into ad-hoc instru
r
instrumentation. However, I keep running into ad-hoc instrumentation being
brittle, which is why I'm interested in first-class support. I think the
only sustainable path forward is that gems natively support some form of
tracing, either through AS::N (which would need to be extracted) o
With the advent of OpenTracing (https://opentracing.io) along with an
official Ruby library (https://github.com/opentracing/opentracing-ruby) as
well as growing industry support
(e.g. https://www.datadoghq.com/blog/opentracing-datadog-cncf/ and
http://blog.scoutapp.com/articles/2018/01/17/tutor
