mimir
mimir copied to clipboard
Docs: Add Documentation to do HA deduplication on Mimir Helm Deployment
What this PR does
Add Documentation to do HA deduplication on Mimir Helm Deployment.
Which issue(s) this PR fixes or relates to
Fixes #2597
Checklist
- [ ] Tests updated
- [X] Documentation added
- [x]
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]
@krajorama please help to do another pass when you are free. I will unset draft from this PR too now.
Changes from your first pass:
- Removed install mimir step and make mimir installated as prerequisite
- Because reference to install mimir is removed therefore I don't see it makes sense to keep Prometheus helm install guide too
- Removed grafana port forwarding and data source setup
- Added Grafana agent setup (although the config and setup are exactly same like Prometheus)
The image docs/sources/operators-guide/configure/setting-helm-ha-deduplication-consul/verify-deduplication.png is unreadable. Do you have one that has higher readability?
The CHANGELOG has just been cut to prepare for the next Mimir release. Please rebase main and eventually move the CHANGELOG entry added / updated in this PR to the top of the CHANGELOG document. Thanks!
The image docs/sources/operators-guide/configure/setting-helm-ha-deduplication-consul/verify-deduplication.png is unreadable. Do you have one that has higher readability?
I updated the image with a higher resolution
This is looking good to me now overall. I wonder where to add some information about using sharding in prometheus operator that I discovered during a support case: https://github.com/grafana/support-escalations/issues/4030#issuecomment-1262289642
I'm fine to add it in a separate PR though after we merge this.
This is looking good to me now overall. I wonder where to add some information about using sharding in prometheus operator that I discovered during a support case: https://github.com/grafana/support-escalations/issues/4030#issuecomment-1262289642
I'm fine to add it in a separate PR though after we merge this.
Yes most likely it is better to be covered in separate PR. I am still more than happy to work on that.