This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Overview

1: Server Type
2: Monitoring Metrics

Service Overview

Event Streams provides fully managed creation and configuration of the open source Apache Kafka for large-scale, massive message data processing. Samsung Cloud Platform automates the creation and configuration of Apache Kafka through a web-based console, and users can configure the main components of Apache Kafka—Broker, Zookeeper, and AKHQ—in a single or clustered form.

Event Streams cluster is composed of multiple Broker nodes, and Brokers can be installed from a minimum of 1 to a maximum of 10, typically installed with 3 or more. Zookeeper can be installed separately to manage the distributed Brokers, and if not installed separately, it is installed together on the Broker node. Additionally, a tool for managing Kafka called AKHQ (Apache Kafka HQ) is provided, allowing users to manage cluster operations through it.

Provided Features

Event Streams provides the following features.

Auto Provisioning (Auto Provisioning): You can configure and set up an Apache Kafka cluster via the UI.
Operation Control Management: Provides a function to control the status of running servers. Restart is possible to apply configuration values, along with starting and stopping the cluster.
Providing AKHQ: By providing AKHQ, a tool that can manage Kafka, users can manage and monitor clusters through it.
Broker node addition: If expansion is needed to improve cluster performance and stability, you can add nodes with the same specifications as the Broker nodes in use.
Parameter Management: Performance improvement and security-related configuration parameters can be set and modified.
Monitoring: CPU, memory, and cluster performance monitoring information can be viewed through the Cloud Monitoring service.

Components

Event Streams provides pre-validated engine versions and various server types in accordance with the open source support policy. Users can select and use them according to the scale of the service they wish to configure.

Engine Version

The engine versions supported by Event Streams are as follows.

Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.

According to the supplier’s policy, the EOS and EoTS dates may change, so please refer to the supplier’s license management policy page for details.

Apache Kafka: https://docs.confluent.io/platform/current/installation/versions-interoperability.html

Notice

Apache Kafka 3.9.1 version is scheduled to be provided after December 18, 2025. The actual service provision schedule may change.

Provided Version	EoS Date	EoTS Date
3.8.0	2026-06 (scheduled)	2026-12-02

Table. Engine versions provided for Event Streams

Server Type

The server types supported by Event Streams are as follows.

For detailed information about the server types provided by Event Streams, please refer to Event Streams Server Types.

Standard ess1v2m4

Category	Example	Detailed description
Server Type	Standard	Provided Server Types Standard: Standard specifications (vCPU, Memory) configuration commonly used High Capacity: Large-capacity server specifications of 24 vCores or more
Server Specifications	ess1	Provided Server Specifications ess1, ess2: Standard specifications (vCPU, Memory) configuration commonly used esh2: Large-capacity server specifications Provides servers with 24 vCores or more
Server specifications	v2	Number of vCores v2: 2 virtual cores
Server Specifications	m4	Memory Capacity m4: 4GB Memory

Table. Event Streams server type components

Preceding Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service for details and prepare in advance.

Service Category	Service	Detailed Description
Networking	VPC	A service that provides an independent virtual network in a cloud environment

Table. Event Streams Preceding Service

1 - Server Type

Event Streams server type

Event Streams provides a server type composed of various combinations such as CPU, Memory, Network Bandwidth, etc. When creating Event Streams, Apache Kafka is installed according to the selected server type suitable for the purpose of use.

The server types supported in Event Streams are as follows.

Standard ess1v2m4

Classification	Example	Detailed Description
Server Type	Standard	Provided server type distinction Standard: Composed of standard specifications (vCPU, Memory) commonly used High Capacity: Server specifications with higher capacity than Standard
Server Specifications	ess1	Classification of provided server type and generation ess1: s means general specifications, and 1 means generation esh2: h means large-capacity server specifications, and 2 means generation
Server Specification	v2	Number of vCores v2: 2 virtual cores
Server Specification	m4	Memory Capacity m4: 4GB Memory

Table. Event Streams server type formats

Reference

Please select the server type by checking the node’s minimum specifications as follows.

Division	vCPU	Memory
Broker	2 vCore	4 GB
Zookeeper	1 vCore	2 GB

ess1 server type

The ess1 server type of Event Streams is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor Supports up to 16 vCPUs and 64 GB of memory
Up to 12.5 Gbps networking speed

Classification	Server Type	vCPU	Memory	Network Bandwidth
Standard	ess1v1m2	1 vCore	2 GB	Up to 10 Gbps
Standard	ess1v2m4	2 vCore	4 GB	Up to 10 Gbps
Standard	ess1v2m8	2 vCore	8 GB	Up to 10 Gbps
Standard	ess1v4m8	4 vCore	8 GB	Up to 10 Gbps
Standard	ess1v4m16	4 vCore	16 GB	Up to 10 Gbps
Standard	ess1v8m16	8 vCore	16 GB	Up to 10 Gbps
Standard	ess1v8m32	8 vCore	32 GB	Up to 10 Gbps
Standard	ess1v16m32	16 vCore	32 GB	Up to 12.5 Gbps
Standard	ess1v16m64	16 vCore	64 GB	Up to 12.5 Gbps

Table. Event Streams server type specification - ess1 server type

ess2 server type

The ess2 server type of Event Streams is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
Supports up to 16 vCPUs and 64 GB of memory
Up to 12.5 Gbps networking speed

Classification	Server Type	CPU vCore	Memory	Network Bandwidth(Gbps)
Standard	ess2v1m2	1 vCore	2 GB	Up to 10 Gbps
Standard	ess2v2m4	2 vCore	4 GB	Up to 10 Gbps
Standard	ess2v2m8	2 vCore	8 GB	Up to 10 Gbps
Standard	ess2v4m8	4 vCore	8 GB	Up to 10 Gbps
Standard	ess2v4m16	4 vCore	16 GB	Up to 10 Gbps
Standard	ess2v8m16	8 vCore	16 GB	Up to 10 Gbps
Standard	ess2v8m32	8 vCore	32 GB	Up to 10 Gbps
Standard	ess2v16m32	16 vCore	32 GB	Up to 12.5 Gbps
Standard	ess2v16m64	16 vCore	64 GB	Up to 12.5 Gbps

Table. Event Streams Server Type Specifications - ess2 Server Type

esh2 server type

The esh2 server type of Event Streams is provided with high-capacity server specifications and is suitable for database workloads for large-scale data processing.

Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
Supports up to 32 vCPUs and 128 GB of memory
Up to 25Gbps networking speed

Division	Server Type	vCPU	Memory	Network Bandwidth
High Capacity	esh2v32m64	32 vCore	64 GB	Up to 25 Gbps
High Capacity	esh2v32m128	32 vCore	128 GB	Up to 25 Gbps

Table. Event Streams server type specification - esh2 server type

2 - Monitoring Metrics

Event Streams Monitoring Metrics

The following table shows the performance monitoring metrics of Event Streams that can be checked through Cloud Monitoring. For detailed usage of Cloud Monitoring, please refer to the Cloud Monitoring guide.

For server monitoring metrics of Event Streams, please refer to the Virtual Server Monitoring Metrics guide.

Performance Item	Detailed Description	Unit
AKHQ State [PID]	AHKQ process PID	PID
Connections [Zookeeper Client]	Number of ZooKeeper connections	cnt
Disk Used	datadir usage	bytes
Failed [Client Fetch Request]	Number of failed client fetch requests	cnt
Failed [Produce Request]	Number of failed produce requests	cnt
Incomming Messages	Number of messages received by the broker	cnt
Instance State [PID]	Kafka process PID	PID
Kibana state [PID]	Kibana process PID	PID
Leader Elections	Number of leader elections	cnt
Leader Elections [Unclean]	Number of unclean leader elections	cnt
Log Flushes	Number of log flushes	cnt
Network In Bytes	Total bytes received by all topics	bytes
Network Out Bytes	Total bytes sent by all topics	bytes
Rejected Bytes	Total bytes rejected by all topics	bytes
Request Queue Length	Request queue size	cnt
Shards	Number of cluster shards	cnt
Zookeeper Sessions [Closed]	Number of ZooKeeper sessions closed per second	cnt
Zookeeper Sessions [Expired]	Number of ZooKeeper sessions expired per second	cnt
Zookeeper State [PID]	Zookeeper process PID	PID

Table. Event Streams Monitoring Metrics