Component Configuration

This section contains detailed configuration documentation for all monitoring components that can be deployed with the Qubership Monitoring Operator.

Component Categories

Core Monitoring Stack

• AlertManager - Alert routing, grouping, and notification management
• Grafana - Visualization and dashboard platform
• VictoriaMetrics - Time series database and storage

Prometheus Stack

• Prometheus - Time series database and monitoring engine
• Prometheus Operator - Prometheus instance management
• Prometheus Rules - Alerting and recording rules
• Prometheus Adapter - Kubernetes custom metrics API

Exporters

• Node Exporter - Hardware and OS metrics
• Kube State Metrics - Kubernetes object state metrics
• Blackbox Exporter - External endpoint probing
• Cert Exporter - TLS certificate monitoring
• Version Exporter - Version tracking
• Network Latency Exporter - Network latency measurements

Cloud Exporters

• CloudWatch Exporter - AWS CloudWatch metrics
• Promitor Agent - Azure Monitor metrics
• Stackdriver Exporter - Google Cloud metrics

VictoriaMetrics Operators

• VM Operator - VictoriaMetrics operator management
• VM Agent - Metrics collection agent
• VM Alert - Alerting component
• VM AlertManager - Alert management
• VM Auth - Authentication proxy
• VM Single - Single-node VictoriaMetrics
• VM User - User management

Additional Components

• Pushgateway - Push-based metrics collection
• Promxy - Prometheus proxy and aggregator
• Graphite Remote Adapter - Graphite protocol support

Common Configuration Patterns

Authentication

TLS Configuration

Resource Management

All components support resource requests and limits configuration:

resources:
  requests:
    cpu: 100m
    memory: 128Mi
  limits:
    cpu: 200m
    memory: 256Mi

Ingress Configuration

Web-based components (Grafana, AlertManager, VictoriaMetrics) can be exposed via ingress:

ingress:
  install: true
  host: component.example.com
  annotations:
    kubernetes.io/ingress.class: nginx

Security Context

Components can run with specific security contexts:

securityContext:
  runAsUser: 2000
  fsGroup: 2000
  runAsNonRoot: true

Next Steps

1. Review component-specific configuration files above
2. See Examples for complete configuration examples
3. Check Configuration Best Practices