Daniel Schierbeck
Daniel Schierbeck
Can you try to see if #219 resolves this issue?
I think a better solution would be to have a notion of data types for tags, with URLs being one type. So you'd do e.g. `trace.set_tag("foo.url", "http://hdhfdsh.com", type: :url)`. Would...
@delner would your suggested pipeline-based approach not incur a significant overhead?
> On a different note, would it make sense to quantize all URLs the same way? Or in practice, would some scenarios require some URLs be quantized differently than others?...
I mean... the HTTP spec only defines so many headers that contain URLs.
I think it's fine to support tooling for that, but out of the box, the default headers should "just work". In general, I'm more interested in the default config being...
@delner my personal reason would be to be able to find traces based on aggregate SQL/view render time in order to debug outliers.
We'd be interested in `stale-if-error` as well, as our current resilience layer is sort of ad-hoc. However, would [`max-stale`](https://tools.ietf.org/html/rfc7234#section-5.2.1.2) not suffice?
Yeah – I can see why that would be counter-intuitive. The reason is that the above code is equivalent to ``` {{@user}} {{#admin?}} The user {{name}} is an admin! {{/admin?}}...