Added ingester limit configurations

General MR

Summary

Overrides default initial ingester limits and sets them to minimal values required for deployment with our monitoring setup.

NOTE: These values may need to be adjusted over time as we learn more about the requirements, but these initial values work with our base monitoring configs

Relevant logs/screenshots

(Include any relevant logs/screenshots)

Linked Issue

issue

Upgrade Notices

N/A

Closes #36 (closed)

added statusready-to-work teamObservability labels

assigned to @bjacksonfv

added 1 commit

• 0531dcc4 - Added out_of_order_time_window

Compare with previous version

changed the description

marked this merge request as ready

requested review from @steven.donald, @blairbowden, @peter.sigur, @piotr.machaj, @kliu, @kscheunemann, and @zcallahan

added statusreview label and removed statusready-to-work label

@bjacksonfv I wouldn't sweat too much about this configuration being too generous. The main point of the low limits is to keep you from blowing your S3 spend when you first spin up Mimir. I know even with values similar to these, I was barely breaking $10/month in S3 spend for our whole observability bucket (loki/mimir/tempo combined) in my production clusters.

approved this merge request

This worked for me. Still getting other errors, but the ingester limit complaints are gone.

merged

mentioned in commit 281deedf