XMLWordPrintable

    • Icon: Outcome Outcome
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • PM Monitoring
    • None
    • False
    • None
    • False
    • Not Selected
    • 0
    • 90% To Do, 10% In Progress, 0% Done

      Proposed title of this feature request

      Nokia Alerting requirements

      What is the nature and description of the request?

      As part of the integration of Nokia’s products with OpenShift Nokia need to be able to map alerts generated by the OpenShift platform and any installed operators to alarms which the Nokia products will raise into Nokia’s Mobile Network Operator customers’ alarm management systems.

      Nokia’s mobile network operator customers expect Nokia to provide a list and description of all alarms, for each release of Nokia’s products, ahead of the Nokia software being available to enable the mobile network operator customer to plan how to integrate those alarms into the mobile network operator customer’s alarm management system in advance of Nokia software being available.

      In order to meet the expectations of Nokia’s mobile network operator customers, Nokia have requested:

      • Every alert that can be generated by Red Hat OpenShift and any Red Hat provided Operators are publicly documented as well as having details of all alerts available in a machine consumable form (e.g. JSON).
      • Alerts must include which operator or component they were generated by.
      • For new releases of OpenShift any additions or changes to alerts are documented so that Nokia does not have to work out the delta for themselves.
      • For new releases of OpenShift the alert documentation (including any delta between releases) is made available ahead of the OpenShift software release.
      • That 3GPP attributes defined in 3GPP spec 32.111 be added to all alerts generated by Red Hat OpenShift and any Red Hat provided Operators, at a minimum the eventType attribute (listed in 3GPP spec 32.111-2 Annex A) and probableCause attribute (listed in 3GPP spec 32.111-2 Annex B) must be included in all alerts.

      Priority should be given to the following list of platform alerts:

      RH-OCP Rule - Name Alert Rules
      default-storage-classes.rules MultipleDefaultStorageClasses
      storage-operations.rules PodStartupStorageOperationsFailing
      openshift-dns.rules CoreDNSErrorsHigh, CoreDNSHealthCheckSlow, CoreDNSPanicking
      etcd etcdDatabaseHighFragmentationRatio, etcdDatabaseQuotaLowSpace, etcdExcessiveDatabaseGrowth, etcdHighCommitDurations, etcdHighFsyncDurations, etcdHighNumberOfFailedProposals, etcdMemberCommunicationSlow, etcdMembersDown, etcdNoLeader,
      control-plane-cpu-utilization ExtremelyHighIndividualControlPlaneCPU, HighOverallControlPlaneCPU,
      pod-security-violation PodSecurityViolation
      extremely-high-individual-control-plane-memory ExtremelyHighIndividualControlPlaneMemory, high-overall-control-plane-memory, mcd-drain-error, mcd-kubelet-health-state-error, mcd-pivot-error, mcd-reboot-error, system-memory-exceeds-reservation,
      high-overall-control-plane-memory HighOverallControlPlaneMemory, mcd-drain-error, mcd-kubelet-health-state-error, mcd-reboot-error, system-memory-exceeds-reservation
      kubernetes-apps KubeContainerWaiting, KubeDaemonSetMisScheduled, KubeDaemonSetNotScheduled, KubeDaemonSetRolloutStuck, KubeDeploymentGenerationMismatch, KubeHpaMaxedOut, KubeHpaReplicasMismatch, KubeJobFailed, KubeJobNotCompleted, KubePodCrashLooping, KubePodNotReady, KubeStatefulSetGenerationMismatch, KubeStatefulSetReplicasMismatch, KubeStatefulSetUpdateNotRolledOut,
      Kubernetes-resources KubeCPUOvercommit, KubeCPUQuotaOvercommit, KubeMemoryOvercommit, KubeMemoryQuotaOvercommit, KubeQuotaAlmostFull, KubeQuotaExceeded, KubeQuotaFullyUsed,
      kubernetes-storage KubePersistentVolumeErrors, KubePersistentVolumeFillingUp, KubePersistentVolumeInodesFillingUp,
      kubernetes-system-kubelet KubeNodeUnreachable
      openshift-general.rules TargetDown
      openshift-kubernetes.rules KubePodNotScheduled
      node-network NodeNetworkInterfaceFlapping

       

              rh-ee-rfloren Roger Florén
              rh-ee-rfloren Roger Florén
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: