4 Commits

Author SHA1 Message Date
Kyle Brennan
aaa928c67d
[proxy] treat errors for /analytics as 503 (#19970)
Elevations of 502 errors for Proxy can trigger ProxyBadGateway, which can be a warning that end-users are having trouble (like if supervisor is returning 502s).

Sometimes /analytics returns 502, like with Enterprise, if telemetry-exporter has trouble. In these scenarios, we do not need/want to trigger ProxyBadGateway (which alerts on-call).

So, for /analytics errors, we return a response code of 503, instead of 502.
2024-06-26 15:03:21 +02:00
Anton Kosyakov
16221d53f9
[analytics plugin] allow to configure segment endpoint (#17593)
in case of dedicated we would like to stream to telemetry exporter instead
2023-05-12 18:21:57 +08:00
Anton Kosyakov
73f98a0e36
[analytics] use dummy static key for untrusted (#17293)
instead of real to unblock Node.js Segment SDK
2023-04-20 17:07:52 +08:00
Anton Kosyakov
bf65f38734
[proxy] add analytics endpoint 2023-04-17 10:28:19 +02:00