Loading...

XML

Word

Printable

Type: Task
Resolution: Done
Priority: Undefined
Fix Version/s: Logging 5.4.0
Affects Version/s: None
Component/s: Log Storage, Loki
Labels:
- collab
- no-doc
- no-qe

Story Points:
2
Blocked:
False
Ready:
False
Epic Link:
Loki Operator Tech Preview
Docs QE Status:
NEW
Feature Link:
OBSDA-7 - Adopting Loki as an alternative to Elasticsearch to support more lightweight, easier to manage/operate storage scenarios
QE Status:
VERIFIED
Market:

Sprint:
Logging (LogExp) - Sprint 210, Logging (LogExp) - Sprint 208, Logging (LogExp) - Sprint 209, Logging (LogExp) - Sprint 211

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Provide an enhancement proposal for the LokiStack Observability features managed by the Loki-Operator, that includes:

Operational alerts for Loki (See initial draft reference)
Per Alert describe the underlying prometheus query and threshold
Per Alert propose a couple of steps for recovery (These should not be the comprehensive set of playbook steps, but a rough description)
If any underlying prometheus rules are used, provide each one as a prometheus query.

is related to

LOG-1799 Add cluster-monitoring recording rules and alerts to manage Loki cluster health

Closed

LOG-2339 [loki-operator] Lokistack alerts status

Closed

links to

openshift/enhancements#940: [WIP] [LOG-1815] Enhancement proposal: Add alerts and rules for operator-managed LokiStack

Assignee:: Ronen Schaffer (Inactive)

Reporter:: Periklis Tsirakidis

Votes:: 1 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2021/10/11 9:15 AM

Updated:: 2022/09/09 7:16 AM

Resolved:: 2021/12/06 10:05 AM