Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve runbook for MimirRequestErrors, Alertmanager section, for alertmanager distributor problems #5694

Merged
merged 3 commits into from
Aug 9, 2023
Merged

Improve runbook for MimirRequestErrors, Alertmanager section, for alertmanager distributor problems #5694

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
24b8edc
Improve request errors runbook if there are am distributor problems
alexweav Aug 7, 2023
2c9a217
Update changelog
alexweav Aug 7, 2023
5fe9088
Regenerate docs
alexweav Aug 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,7 @@
* [ENHANCEMENT] Improved `MimirRulerTooManyFailedQueries` runbook. #5586
* [ENHANCEMENT] Improved "Recover accidentally deleted blocks" runbook. #5620
* [ENHANCEMENT] Documented options and trade-offs to query label names and values. #5582
* [ENHANCEMENT] Improved `MimirRequestErrors` runbook for alertmanager. #5694

### Tools

Expand Down
4 changes: 4 additions & 0 deletions docs/sources/mimir/manage/mimir-runbooks/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -286,6 +286,10 @@ How to **investigate**:
- Looking at `Mimir / Alertmanager` dashboard you should see in which part of the stack the error originates
- If some replicas are going OOM (`OOMKilled`): scale up or increase the memory
- If the failing service is crashing / panicking: look for the stack trace in the logs and investigate from there
- If the `route` label is `alertmanager`, check the logs for distributor errors containing `component=AlertmanagerDistributor`
- Check if instances are starved for resources using the `Mimir / Alertmanager resources` dashboard
- If the distributor errors are `context deadline exceeded` and the instances are not starved for resources, increase the distributor
timeout with `-alertmanager.alertmanager-client.remote-timeout=<timeout>`. The defaut is 2s if not specified.

### MimirIngesterUnhealthy

Expand Down
Loading