OTEL Stack Resource Requirements

Prerequisite resource requirements for deploying the DuploCloud OTEL stack

The DuploCloud OpenTelemetry (OTEL) stack requires specific resources for deployment. The implementation features node-level components, deployed as DaemonSets, for telemetry collection and central observability components for data aggregation, processing, and visualization. Object storage is the backbone for retaining metrics, logs, traces, and profiling data, ensuring scalability and long-term accessibility.

OTEL Resource Requirements

Node-Level Components (DaemonSet)

The following components run as DaemonSets on each node in the Kubernetes cluster.

Component	CPU Limit	Memory Limit	Purpose
alloy-logs	0.5 cores	512 MB	Log collection and forwarding
alloy-profiles	0.5 cores	300 MB	Continuous application profiling
node-exporter	0.1 cores	50 MB	Hardware and OS metrics export
Beyla	0.5 cores	512 MB	Automatic application instrumentation

Central Stack Components

Hardware Requirements

Configuration	Hardware Requirements
Recommended Configuration	CPU: 8 cores | Memory: 32 GB RAM
Minimum Viable Configuration	CPU: 4 cores | Memory: 16 GB RAM

Core Services Resource Allocation

Service	CPU Allocation	Memory Allocation	Purpose
Loki	1-3 cores	4-12 GB	Log aggregation
Mimir	1-3 cores	4-12 GB	Metrics storage
Tempo	1-2 cores	2-8 GB	Distributed tracing
Pyroscope	1-2 cores	2-8 GB	Continuous profiling

Supporting Components

Component	CPU Allocation	Memory Allocation	Purpose
Alloy StatefulSet	1 core	2 GB	Centralized metrics collection
OTEL Collector	1 core	2 GB	Telemetry processing
kube-state-metrics	0.1 cores	50 MB	Kubernetes object metrics

Storage Configuration

The implementation uses object storage (e.g., S3, GCS, Azure Storage Account) for:

• Metrics storage (Mimir)

• Log storage (Loki)

• Trace storage (Tempo)

• Profile data storage (Pyroscope)