Monitoring and billing
Read receiver delivery reports in the console, review delivery periods and billed IP-days, and keep prepaid credit available for the stream.
Open Shredstream for your team in the console. Delivery figures are measured by the sending edges. They do not confirm reception by your application; monitor your receiver's socket and processing as well.
Receivers panel
The Receivers panel shows:
| Column | Meaning |
|---|---|
| UDP destination | Receiver IPv4 address and UDP port. |
| Metro | Metro whose edge sends to the receiver. |
| State | Whether the receiver is active, paused or blocked by its prepaid balance. |
| Packets/s | Packet rate measured at the sending edge. |
| Mb/s | Traffic rate measured at the sending edge. |
| Clone errors/s | Packets the edge failed to clone to the receiver. |
| Last report | Time of the latest edge report, or Not reporting when no report is available. |
| Packets/s, 1 h | Packet-rate history over the last hour. |
Rates cover a 2-minute window and refresh every 10 seconds. A reported sending rate is not proof that every datagram reached your application.
Receiver states are:
| State | Meaning |
|---|---|
active | Receiver is configured for delivery. |
paused | ZeroCopy has paused delivery. |
blocked_balance | Delivery is blocked because prepaid credit is exhausted. |
For missing traffic, check the receiver setup. For a receiver change or pause, contact support.
Delivery periods
Delivery periods shows the last 30 days of delivery: receiver, metro, IP, start, end and duration. IP-days are counted from the periods when delivery was on. Changing an active receiver's address or metro starts a new period.
Billed days
Billed days shows the last 30 UTC days with the IP-day quantity, cost and billing status. Day not finished identifies a UTC day still in progress. Not reported yet means billing for that day has not yet been reported.
IP-day billing
Shredstream is charged per receiver IP per metro, billed per IP-day from prepaid credit. An IP-day counts a receiver IPv4 address in one metro with delivery on during a UTC day. Additional ports on the same IP in the same metro cost nothing more. The same IP in another metro is counted separately. See the pricing page for the current rate.
Billing starts from the day a receiver becomes active. The delivery and metering records are the basis of charges, rather than the number of packets your application processes.
Delivery stops when prepaid credit is exhausted and resumes after a top-up. SWQoS sending is unaffected and does not require prepaid credit. Usage already in progress can take the balance below zero; that amount is deducted from the next credit purchase. See Terms 4.3.