Metrics Information Categories

This observability solution will capture end to end metrics for all the infrastructure deployed as part of a Siebel CRM deployment done by SCM.

Here are the categories of metric information that are captured and displayed on sample dashboards delivered as part of this solution:

• Node Metrics
• Container Metrics
• Kubernetes Metrics
• Ingress-Nginx Controller Metrics
• OCI Infrastructure Service Metrics
• Metrics for Java-based Services in Siebel CRM
• Siebel Server Metrics

Node Metrics

Capture and propagate hardware-level metrics from each node in the cluster. For example, CPU usage, memory consumption, disk I/O, network statistics, and so on. Node Exporters are used to collect these metrics.

• For more information on node exporters, refer https://github.com/prometheus/node_exporter.
• For a detailed list of all available metrics, refer to the "Prometheus Server Node Metrics" section in Monitoring & Alerting Capabilities in an Oracle Private Cloud Appliance X9-2 (PDF).

Container Metrics

The Siebel Observability solution captures and propagates container-level metrics like CPU and memory usage, file system statistics, network activities, and so on. cAdvisor is used to collect metrics.

• For more information on cAdvisor, refer https://github.com/google/cadvisor/tree/master.
• More details about cAdvidor and all available metrics, refer https://github.com/google/cadvisor/blob/master/docs/storage/prometheus.md.

Kubernetes Metrics

Information about the state and health of various Kubernetes objects like pods, deployments, services, and so on are captured. For example, Kubernetes objects CPU, memory consumption, disk I/O, network statistics among others. "kube-state-metrics", which is a service that listens to the Kubernetes API server and generates metrics about the state of the objects, are used.

• For more information on kube-state-metrics, refer https://github.com/kubernetes/kube-state-metrics/tree/main.
• For a detailed list of all available metrics, refer https://github.com/kubernetes/kube-state-metrics/blob/main/docs/metrics/workload/pod-metrics.md.

Ingress-Nginx Controller Metrics

Metrics are also collected about Ingress-Nginx Controllers. These help in the monitoring and management of ingress traffic by measuring, for example, total number of client requests, sum of response duration per ingress, request processing time, upstream service latency per ingress, and so on. This observability solution uses ingress-nginx exporters for collecting metrics for Prometheus to scrape.

• For more information on ingress-nginx exporters, refer https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/monitoring.md.
• For a detailed list of all available metrics, refer https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/monitoring.md#exposed-metrics.

OCI Infrastructure Service Metrics

In this category, the observability – monitoring solution relays data about the health, capacity, and performance of cloud resources on OCI. A wide array of metrics for OCI services in use, like database, network, vault, and so on, are available. Metrics and Alarms features of OCI Monitoring Service are used to collect these.

For more information, refer https://docs.oracle.com/en-us/iaas/Content/Monitoring/Concepts/monitoringoverview.htm.

Metrics for Java-based Services in Siebel CRM

For metrics categories belong to Java services used in Siebel CRM, Java Management Extension (JMX) exporters are used. JMX in Gateway, Siebel Server, AI and SMC pods help in collecting necessary metrics.

For more information on JMX exporters, refer https://github.com/prometheus/jmx_exporter.

Siebel Server Metrics

This category of metrics help in monitoring important aspects of the Siebel application servers. Siebel Server related metrics are collected through custom monitoring agents. The following out-of-the-box metrics are collected:

Max_Tasks, Total_Tasks, Active_Tasks, Total_Siebel_Servers, Active_Siebel_Servers, Active_Processes, Max_Mts_Process, Active_Mts_Process, Active_Sessions, Siebel_Server_State, SIEBEL_COMPONENT_INFO, SIEBEL_COMPGRP_INFO, SIEBEL_TASK_INFO, SIEBEL_PROCESS_INFO, SIEBEL_SESSION_INFO, and so on.

The framework allows collection and propagation of more Siebel information to be collected as metrics by processing server manager commands.