The “Write Bandwidth” is based on the payload size of each streaming write.

RabbitMQ clients will incur a “RabbitMQ Write Bandwidth” charge in addition to the standard “Write Bandwidth” charge.

The minimum message byte size is 512 bytes. Messages smaller than 512 bytes will be charged as if they were 512-byte messages.

The “Read Bandwidth” is based on the payload size of each streaming read.

RabbitMQ clients will incur a “RabbitMQ Read Bandwidth” charge in addition to the standard “Read Bandwidth” charge.

The minimum message byte size is 512 bytes. Messages smaller than 512 bytes will be charged as if they were 512-byte messages.

“Storage” means all messages persisted onto storage disk.

Storage is calculated based on logical storage consumption. Storage is measured in GB per month, using the maximum data stored in the given month for the usage calculation.

“Topic/Partitions” means the channel used to pass messages published by producers to consumers who process those messages.

Topic-partitions are measured per hour.

A “Function Instance” means a unit used for scaling Pulsar functions or Pulsar IO connectors running on Astra Streaming.

Each Function Instance is assigned a specific amount of CPU and memory which can be allocated to a Pulsar function. Each Pulsar function running on Astra Streaming will have a minimum of one Function Instance allocated to it.

Function instances are measured per hour.

“Function Read Bandwidth” is based on the payload size of each function read.

Function read bandwidth is the egress traffic measured in GB coming out of a function (or connector).

“Function Write Bandwidth” is based on the payload size of each function write.

Function write bandwidth is the ingress traffic measured in GB coming into a function (or connector).

The “Metrics Read” is based on the payload size of each streaming metrics read.

Metrics reads are measured in GB.