For each write to Thanos/receive, add limit to the allowed number of samples

[spaparaju]

Is your proposal related to a problem?

Yes

Currently Thanos based hosted monitoring services lack protection to limit the number of samples that can be accepted at 'Thanos receive' component.

Describe the solution you'd like

For each write call, define a configurable upper bound (at Thanos receive component) to the number of samples that can be received.

Describe alternatives you've considered

None

Additional context

PR for this proposal : #3963

[metalmatze]

I'm wondering if that should be really part of the Thanos Receiver and not some other proxy in front of the Receiver.
Maybe it still fits into the Receiver Route once the Receiver is split into Receiver and Receiver Route?

[stale]

Hello 👋 Looks like there was no activity on this issue for the last two months.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity in the next two weeks, this issue will be closed (we can always reopen an issue if we need!). Alternatively, use remind command if you wish to be reminded at some point in future.

[spaparaju]

The idea behind this knob is to protect, configure resources at Receiver pods

[stale]

Hello 👋 Looks like there was no activity on this issue for the last two months.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity in the next two weeks, this issue will be closed (we can always reopen an issue if we need!). Alternatively, use remind command if you wish to be reminded at some point in future.

[stale]

Closing for now as promised, let us know if you need this to be reopened! 🤗

[bill3tt]

still relevant

[spaparaju]

still relevant