Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-1142

Expose recommendations based on cluster health

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • None
    • Log Storage
    • 5
    • NEW
    • NEW
    • Logging (LogExp) - Sprint 204, Logging (LogExp) - Sprint 208

      As a consumer of the Elasticsearch Operator I want to have recommendations and playbooks made available to me based on information collected from the cluster so that I can be better enabled to troubleshoot my cluster and prevent it from reaching a critical state.

       

      Recommendations could include:

      • node sizing
      • number of nodes (topology)
      • backing storage
      • curation rate/age

       

      Notes:

      • Based on number of indices and size of indices
        • figure out how much memory a master node would need
        • how much memory and storage a data node would need
        • how much memory an ingest node would need
        • how much memory a coordinating node would need

       

      Acceptance Criteria:

      • Ensure that our current alerts are informative and point to documentation that describes what the alert means, what further investigation steps can be taken, and what actions can be taken to resolve them.

              Unassigned Unassigned
              ewolinet@redhat.com Eric Wolinetz (Inactive)
              Rolfe Dlugy-Hegwer Rolfe Dlugy-Hegwer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: