Monitoring data processed

Events

For a rough estimate of the number of events, go to the AIOps Insights dashboard. The AIOps Insights dashboard can be accessed from the administration page of IBM Cloud Pak for AIOps, under Overview > Quick navigation > AIOps insights. Alternatively, click the navigation icon (four horizontal bars) to go to the main navigation menu. Then, click Operate > AIOps insights.

The noise reduction graph shows the number of events over the selected time period, such as 24 hours, 7 days, or 30 days. You can use the average of the events when you use the Cloud Pak for AIOps deployment sizing.

For more information about precise distribution of events, see Enabling monitoring for user-defined projects.

When the OpenShift user workload monitoring is enabled, you can view the metrics in the OpenShift dashboard.

The following Prometheus query can be used to view the number of events, which can be added in the Cloud Pak for AIOps console console under Observe > Metrics:

sum(irate((flink_taskmanager_job_task_operator_KafkaSourceReader_topic_partition_currentOffset{topic="cp4waiops_cartridge_lifecycle_input_events"}>0)[1m:30s]))

Topology

To view the number of resources, click Resource Management, and view the resource count. For example, you can see 864 resources in the following example.

For more information about the Resource management, see The Resource management page.

Logs

To view the number of logs, extract the count from the Elastic backend:

1. Log in to your Red Hat® OpenShift® cluster, or SSH into a control plane node or the loadbalancer VM on your Linux® deployment. Then swtich to the namespace where IBM Cloud Pak for AIOps is installed.

   oc project <project>
   

   Where <project> is the project that your IBM Cloud Pak for AIOps installation is deployed in.

2. Run the following commands to determine the names of the log data indices:

   export ELASTIC_SET="$(oc get statefulset -l app.kubernetes.io/managed-by=ibm-elasticsearch -o jsonpath='{.items[0].metadata.name}')"
   oc exec "statefulset/${ELASTIC_SET}" -- curl -XGET -k --fail "http://127.0.0.1:19200/_cat/indices?v" | grep logtrain
   

   Example output, where the index name is 1000-1000-20220302-logtrain:

   green open 1000-1000-20220302-logtrain        eEvaBufQ06yG074hmeHKG  8 1 244 6 72.7kb 72.7kb
   

   
   

3. For each log train index, get the document count using the following command:

   export INDEX_NAME=<index_name>
   export ELASTIC_SET="$(oc get statefulset -l app.kubernetes.io/managed-by=ibm-elasticsearch -o jsonpath='{.items[0].metadata.name}')"
   oc exec "statefulset/${ELASTIC_SET}" -- curl -XGET -k --fail "http://127.0.0.1:19200/${INDEX_NAME}/_count"
   

   Where <index_name> is an index name that you found in the previous step.

The outputs of the preceding curl commands provide the daily count of the logs processed. To align with the Cloud Pak for AIOps deployment sizing, you can average the daily count of logs, or pick the maximum value from both of the curl commands.

Metrics

To view the number of Metric KPIs being tracked, click AI Model Management > Metric anomaly detection.

The number of KPIs is noted under the Metrics analyzed field. For example, 146 metrics were analyzed in the following example.

For more information about Metric anomaly detection, see the following links:

• About Metric anomaly detection.
• Setting up training for Metric anomaly detection.