SAS® Viya® Monitoring for Kubernetes

SAS® Viya® Monitoring for Kubernetes provides simple scripts and customization options to deploy monitoring, alerts, and log aggregation for SAS Viya 4.x.

Monitoring and logging may be deployed independently or together. There are no hard dependencies between the two.

Monitoring - Metrics and Alerts

The monitoring solution includes these components and your right to use each such component is governed by its applicable open source license:

• Prometheus Operator
  • Prometheus
  • Alertmanager
  • Grafana
• Prometheus Exporters
  • node-exporter
  • kube-state-metrics
  • Prometheus Adapter for Kubernetes Metrics APIs
  • Prometheus Pushgateway
• Alert definitions
• Grafana dashboards
  • Kubernetes cluster monitoring
  • SAS CAS Overview
  • SAS Java Services
  • SAS Go Services
  • RabbitMQ
  • Postgres
  • Fluent Bit
  • Elasticsearch
  • Istio
  • NGINX

This is an example of a Grafana dashboard for cluster monitoring.

This is an example of a Grafana dashboard for SAS CAS monitoring.

See the documentation at SAS Viya: Monitoring for more information about using the monitoring components.

Logging - Aggregation, Searching, & Filtering

The logging solution includes these components and your right to use each such component is governed by its applicable open source license:

• Fluent Bit

  • Custom Fluent Bit parsers

• Elasticsearch

  • Custom index pattern for logs
  • Namespace separation
  • Elasticsearch Exporter

• Kibana

  • Custom Kibana dashboards

  This is an example of a Kibana dashboard displaying log message volumes.

  

See the documentation at SAS Viya: Logging for more information about using the logging components.

Prerequisites

• A Kubernetes cluster that meets the prerequisites for SAS Viya
• Helm version 3.x
• kubectl version 1.18+ with cluster-admin access
• Git version 1.8 or later
• Bash

Installation

Monitoring

See the monitoring README to deploy the monitoring components, including Prometheus Operator, Prometheus, Alertmanager, Grafana, metric exporters, service monitors, and custom dashboards.

Logging

See the logging README to deploy the logging components, including Fluent Bit, Elasticsearch, and Kibana.

Customization

For most deployment scenarios, the process of customizing the monitoring and logging deployments consists of:

• creating the location for your local customization files
• using the USER_DIR environment variable to specify the location of the customization files
• copying the customization files from one of the provided samples to your local directory
• specifying customization variables and parameters in the customization files

Other scenarios use different customization steps that are specific to each scenario.

Samples are provided for several common deployment scenarios. Each sample includes detailed information about the customization process and values for the scenario.

See the monitoring README and logging README for detailed information about the customization process and about determining valid customization values. See the README file for each sample for detailed information about customization for each deployment scenario.

Default StorageClass

The default cluster StorageClass is used for both monitoring and logging unless the value is overidden in the user-*.yaml files for monitoring or logging. The deployment scripts issue a warning if no default StorageClass is available, even if the value is properly set by the user. In this case, you can safely ignore the warning.