Conduit support for Server-Timing headers?
Brian Smith <br...@...>
Kevin Lingerfelt <k...@buoyant.io> wrote:
Would it be useful for the conduit proxy to start adding Server-TimingI think there are two questions:
1. Should we support adding Server-Timing headers?
2. If so, should we add them by default?
I think it is OK to support them but we shouldn't add them by default.
From a performance perspective, the fewer headers that are sent, the
Server-Timing: emoji-svc;dur=27The cluster operators likely would not want to disclose this
information in general: the names of the underlying services and/or
their performance characteristics might be private for competitive
reasons (details of performance characteristics are often guarded),
business reasons (e.g. an unreleased products' name is encoded in a
service's name), and/or security reasons (e.g. the administrators
don't want to disclose the internal topology of the cluster).
Given that this featureThat's a good point. I don't think it's a matter of "instead" but it
does seem like we'd need some infrastructure for this.
I could also see a case where we'd want this to be a feature of
routing so that the headers are included, say, for developers'
requests but not for typical end-users' requests.
William Morgan <wil...@...>
toggle quoted messageShow quoted text
Agreed this shouldn't be enabled by default. But there's potentially a cool demo we could make around this, since there is starting to be browser support for it. I suggest we keep it on the back burner until we tackle tracing.
On Tue, Feb 13, 2018 at 11:50 AM, Brian Smith <br...@...> wrote:
Kevin Lingerfelt <k...@...> wrote: