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

Return to the regular view of this page.

Overview

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, such as Broker, Zookeeper, and AKHQ, in a single or cluster form.

Event Streams cluster is composed of multiple Broker nodes, and Brokers can be installed from a minimum of 1 up 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. In addition to starting and stopping the cluster, restarting is possible to apply configuration values.
  • AKHQ Provision: AKHQ, a tool that can manage Kafka, is provided, allowing users to manage and monitor clusters through it.
  • Add Broker node: If expansion is required to improve the cluster’s performance and stability, you can add nodes with the same specifications as the existing Broker nodes.
  • Parameter management: Performance improvement and security-related configuration parameter setting and modification are possible.
  • Monitoring: CPU, memory, and performance monitoring information can be checked via Cloud Monitoring and Servicewatch.

Components

Event Streams provides pre-validated engine versions and various server types according to the open source support policy. Users can select and use them according to the scale of the service they want 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.

Provided VersionEoS DateEoTS Date
3.8.02026-06 (scheduled)2026-12-02
3.9.12026-09 (scheduled)2027-02-19
Table. Engine versions provided by 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, see Event Streams Server Types.

Standard ess1v2m4
CategoryExampleDetailed description
Server TypeStandardProvided Server Types
  • Standard: Standard specifications (vCPU, Memory) commonly used
  • High Capacity: Large server specifications of 24 vCore or more
Server Specificationsess1Provided server specifications
  • ess1, ess2: Standard specifications (vCPU, Memory) configuration commonly used
  • esh2: Large-capacity server specifications
    • Provides servers with 24 vCores or more
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server Specificationsm4Memory 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 CategoryServiceDetailed Description
NetworkingVPCA 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
ExampleDetailed Description
Server TypeStandardProvided server type distinction
  • Standard: Composed of standard specifications (vCPU, Memory) commonly used
  • High Capacity: Server specifications with higher capacity than Standard
Server Specificationsess1Classification 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 Specificationv2Number of vCores
  • v2: 2 virtual cores
Server Specificationm4Memory 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.

DivisionvCPUMemory
Broker2 vCore4 GB
Zookeeper1 vCore2 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
ClassificationServer TypevCPUMemoryNetwork Bandwidth
Standardess1v1m21 vCore2 GBUp to 10 Gbps
Standardess1v2m42 vCore4 GBUp to 10 Gbps
Standardess1v2m82 vCore8 GBUp to 10 Gbps
Standardess1v4m84 vCore8 GBUp to 10 Gbps
Standardess1v4m164 vCore16 GBUp to 10 Gbps
Standardess1v8m168 vCore16 GBUp to 10 Gbps
Standardess1v8m328 vCore32 GBUp to 10 Gbps
Standardess1v16m3216 vCore32 GBUp to 12.5 Gbps
Standardess1v16m6416 vCore64 GBUp 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
ClassificationServer TypeCPU vCoreMemoryNetwork Bandwidth(Gbps)
Standardess2v1m21 vCore2 GBUp to 10 Gbps
Standardess2v2m42 vCore4 GBUp to 10 Gbps
Standardess2v2m82 vCore8 GBUp to 10 Gbps
Standardess2v4m84 vCore8 GBUp to 10 Gbps
Standardess2v4m164 vCore16 GBUp to 10 Gbps
Standardess2v8m168 vCore16 GBUp to 10 Gbps
Standardess2v8m328 vCore32 GBUp to 10 Gbps
Standardess2v16m3216 vCore32 GBUp to 12.5 Gbps
Standardess2v16m6416 vCore64 GBUp 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
DivisionServer TypevCPUMemoryNetwork Bandwidth
High Capacityesh2v32m6432 vCore64 GBUp to 25 Gbps
High Capacityesh2v32m12832 vCore128 GBUp to 25 Gbps
Table. Event Streams server type specification - esh2 server type

2 - Monitoring Metrics

Event Streams Monitoring Metrics

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

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

Performance ItemDescriptionUnit
AKHQ State [PID]AHKQ process PIDPID
Connections [Zookeeper Client]Number of ZooKeeper connectionscnt
Disk Useddatadir usage amountbytes
Failed [Client Fetch Request]Number of failed client Fetch request processingcnt
Failed [Produce Request]Number of failed Producer request processingcnt
Incomming MessagesNumber of messages received by Brokercnt
Instance State [PID]kafka process PIDPID
Kibana state [PID]Kibana process PIDPID
Leader ElectionsNumber of Leader Election occurrencescnt
Leader Elections [Unclean]Number of Unclean Leader Election occurrencescnt
Log FlushesNumber of log flush occurrencescnt
Network In BytesBytes received by all Topicsbytes
Network Out BytesBytes sent by all Topicsbytes
Rejected BytesBytes rejected by all Topicsbytes
Request Queue LengthRequest queue sizecnt
ShardsCluster shard countcnt
Zookeeper Sessions [Closed]ZooKeeper closed sessions per secondcnt
Zookeeper Sessions [Expired]Zookeeper expired sessions per secondcnt
Zookeeper State [PID]zookeeper process PIDPID
Table. Event Streams Monitoring Metrics

3 - ServiceWatch Metrics

Event Streams sends metrics to ServiceWatch. The metrics provided by basic monitoring are data collected at a 1‑minute interval.

Reference
To check metrics in ServiceWatch, refer to the ServiceWatch guide.

Basic Indicators

The following are the basic metrics for the namespace Event Streams.

OS Basic Metrics

CategoryPerformance ItemDetailed DescriptionUnitMeaningful Statistics
CPUCPU UsageCPU Usage RatePercent
DiskDisk UsageDisk Usage RatePercent
DiskDisk Write BytesWrite capacity on block device (bytes/second)Bytes/Second
DiskDisk Read BytesAmount read from block device (bytes/second)Bytes/Second
DiskDisk Write RequestNumber of write requests on block device (requests/second)Count/Second
DiskDisk Read RequestsNumber of read requests on block device (requests/second)Count/Second
DiskAverage Disk I/O Queue SizeAverage queue length of requests issued to the block deviceNone
DiskDisk I/O UtilizationProportion of time the block device actually processes I/O operationsPercent
MemoryMemory UsageMemory Usage RatePercent
NetworkNetwork In BytesReceived capacity on the network interface (bytes/second)Bytes/Second
NetworkNetwork Out BytesData transmitted from network interface (bytes/second)Bytes/Second
NetworkTCP ConnectionsTotal number of TCP connections currently established correctlyCount/Second
NetworkNetwork In PacketsNumber of packets received on the network interfaceCount
NetworkNetwork Out PacketsNumber of packets transmitted from the network interfaceCount
NetworkNetwork In DroppedNumber of packet drops received on the network interfaceCount
NetworkNetwork Out DroppedNumber of packet drops transmitted from the network interfaceCount
NetworkNetwork In ErrorsNumber of packet errors received on the network interfaceCount
NetworkNetwork Out ErrorsNumber of packet errors transmitted from the network interfaceCount
Table. OS Basic Metrics

Event Streams Basic Metrics

CategoryPerformance ItemDetailed DescriptionUnitMeaningful Statistics
ActivelockActive locksNumber of active locksCount
ActivesessionActive sessionsNumber of active sessionsCount
ActivesessionConnection usageDB connection session usage ratePercent
ActivesessionConnectionsDB connection sessionCount
ActivesessionConnections(MAX)Maximum number of connections that can be attached to the DBCount
ProxySQLProxy UptimeExpress the proxy’s uptime in secondsSeconds
ProxySQLBackend connections(CONNECTED)Number of sessions connected to the Proxy serverCount
ProxySQLClient connections connectedNumber of client sessions currently connected to the proxyCount
ProxySQLQueries routedNumber of queries routed to backend serverCount
ProxySQLBackend connections(ACTIVE, IDLE)Number of Active / idle connections per EndpointCount
ProxySQLBackend server statusBackend server status
  • 1 - Online
  • 2- SHUNNED
  • 3 - OFFLINE_SOFT
  • 4 - OFFLINE_HARD
  • 5 - SHUNNED_REPLICATION_LAG
None
ProxySQLBackend connection checkBackend server’s connection success/failure checkCount
StateInstance stateScalable DB status up/down checkCount
StateSlave behind master secondsReplica’s delay amount (unit: seconds)Seconds
TablespaceTablespace usedTablespace usageMegabytes
TablespaceTablespace used(TOTAL)Tablespace usage (total)Megabytes
TransactionsSlow queriesNumber of slow queriesCount
TransactionsTransaction timeLong Transaction timeSeconds
TransactionsWait locks LockNumber of waiting sessionsCount
Table. Event Streams basic metrics