Support for refresh interval jitter about unleash-proxy HOT 9 CLOSED

Have you seen this as an actual problem today? Could you share some traffic charts @Meemaw?

Our experience running the proxy for customers in Unleash Cloud is that they usually will never start at the same time, just because of how the scheduler will provision instances.

But, I think actually the main problem is to not have them start sending metrics at the same time, so the first time metrics are sent should actually be random number in the defined metrics interval.

What do you think?

from unleash-proxy.

Actually, it seems posting metrics is the main issue. Here is a chart

from unleash-proxy.

Hey! Sorry for the long delay here 🙋

Yeah, we agree that this sounds like a sensible thing to add. Whether it'd be better to add jitter only for the first send and then send at regular intervals thereafter or to add jitter for every request is still uncertain, but that can be discussed and decided.

Anyway, would you be willing to make a PR for this? We'd be happy to provide guidance, of course 😄

from unleash-proxy.

@thomasheartman this would have to be implemented in each client separately, right? For proxy in particular, that would be node client.

from unleash-proxy.

I think if we only jitter on the initial metrics startup, we would only have to update the unleash-proxy package. PR above.

from unleash-proxy.

@Meemaw @guscost-opensea :

Yeah, if you only add it to the startup, then it should suffice to only update the proxy, but as you mentioned in the PR: it might make more sense to add jitter for every request. That would require updates both to the Node SDK and to the proxy.

from unleash-proxy.

Node SDK v3.18.0-beta.0 introduced support for jitter on the metrics interval.

We need to be mindful that the proxy customize the metrics sligthly (see code)

In addition we need to expose the same jitter option in the proxy (also as an environment variable).

from unleash-proxy.

Released as part of v0.14.0-beta.0.

Do you mind testing it a bit @Meemaw ?

from unleash-proxy.

@ivarconr We still use fairly old version of proxy, mainly due to #86

from unleash-proxy.