Prerequisites

This solution requires the following applications:

  • IBM Cloud Platform Common Services 3.2.4 must be installed prior to install this chart. See the following topic in IBM Documentation: Installing Common Services.
  • IBM Tivoli Netcool/OMNIbus ObjectServer to be created and running prior to installing the probe either on OpenShift Container Platform 4.3 (OCP) with Common Services or on-premise:
  • Scope-based Event Grouping automation to be installed, see the following topic in IBM Documentation: About scope-based event grouping. The probe requires several table fields to be installed in the ObjectServer. For on-premise installation, see Installing scope-based event grouping. The events will be grouped by a preset ScopeId in the probe rules file if the event grouping automation triggers are enabled.
  • Kubernetes 1.14
  • Prometheus 2.3.1 and Prometheus Alert Manager 0.15.0
  • IBM Cloud Event Management Helm Chart 2.5.0
Note: Administrator role is a minimum requirement to install this chart.
The chart must be installed by a Administrator to perform the following tasks:
  • Enable Pod Disruption Budget policy when installing the chart.
  • Perform post-installation tasks such as to configure Prometheus Alert Manager and Logstash in the kube-system namespace to add the probe endpoint.
  • Retrieve and edit sensitive information from a secret such as the credentials to use to authenticate with the ObjectServer or replace the key database files for secure communications with the ObjectServer.
The chart must be installed by a Cluster Administrator to perform the following tasks in addition to those listed above:
  • Obtain the Node IP using kubectl get nodes command if using the NodePort service type.
  • Create a new namespace with custom PodSecurityPolicy if necessary.
  • Create a service account in the namespace for this chart. Perform one of the following actions:
    • Have the Cluster Administrator pre-create the custom service account in the namespace. This installation requires the service account name to specified to install the chart and can be done by an Administrator.
    • Have the Cluster Administrator perform the installation without specifying a service account name so that the chart generates a service account and use it. When the Helm release is deleted, the service account will also be deleted.
  • If secured communication is required or enabled on your Netcool/OMNIbus ObjectService, a per-created secret is required for this chart to establish a secured connection with the ObjectServer.
  • Additional ObjectServer fields are required in the alerts.status table for IBM CEM integration. For details of the Structured Query Language (SQL) needed to add the required fields, see Integrating IBM Cloud Event Management (CEM) with Netcool Operations Insight
  • If you opt to install the chart through command line, then the Helm CLI must be installed. Refer to Installing Helm CLI (helm).