CDN Status Print

  • cdn, status
  • 0

Medusa Panel › System › CDN Status

The CDN Status page is a read-only live dashboard for the built-in content delivery network. It shows which servers are acting as CDN nodes, whether load balancing is active, how much traffic the CDN is handling, how the nodes are linked, and which resources are cached where. The data is refreshed about once per second, so the figures and the topology move in near real time.

If CDN delivery (edge caching, pulls between servers and load balancing) is not implemented in this build, the page still renders but the CDN counters stay at 0. An information banner says so when that is the case.

Load balancing status

A card at the top reports the state of CDN load balancing as a badge:

  • Enabled — new playback sessions are assigned automatically to healthy CDN servers that hold a valid license.
  • Inactive — automatic assignment is off. A short reason is shown, such as Disabled, CDN function is disabled, Offline, Draining, At capacity or CDN unavailable. Manual CDN assignments continue to work even while automatic balancing is inactive.

Above the cards a banner may also warn that CDN function is disabled or that No CDN server configured, which tells you why the counters below are empty.

Summary counters

A row of tiles sums up the whole CDN across all reporting nodes:

  • CDN Servers — how many servers are participating as CDN nodes.
  • Current Users — the total number of viewers currently served by the CDN.
  • Current Down — the combined inbound rate, in Mbps, as nodes pull data.
  • Current Up — the combined outbound rate, in Mbps, as nodes serve clients.
  • Traffic Saved — the volume served from cache instead of from the origin.
  • Cached Data — the total size of cached resources held across the nodes.

A Hit rate badge accompanies the topology and is calculated from cache hits versus total requests, for example Hit rate 92.5%.

CDN Topology

The topology draws one node per server and connects them with arrows that show active cache paths. An arrow points from the upstream server toward the server that is pulling from it (the direction the data flows), and each arrow is labelled with the round-trip time, a smoothed pull rate and the number of resources moving along that path, for example 8.4 ms · 12.30 Mbps · 3 resources.

Arrows linger briefly between HLS segments so that intermittent pulls stay visible rather than flickering. Each node is tagged by role — Edge, Origin or Source — and the server you are viewing is marked as the local node. A server that is only known as a pull target, but is not itself reporting CDN state, appears as a virtual origin node.

CDN Servers

Below the topology each CDN node is shown as a card you can scroll through horizontally. A card gives the server name, an online or offline badge, a local badge for this server and an Edge badge when the node is actively serving as an edge. It also shows the server number and base address, load bars for CPU, Egress, Memory and Disk, and a set of figures:

  • Current down and Current up — the node inbound and outbound rates.
  • Server egress — the overall outbound rate of the machine.
  • Total down and Total up — cumulative transfer.
  • Traffic saved — what the node served from cache.
  • Current users — viewers on that node.
  • Cached resources — how many resources it holds.
  • Last seen — how long ago the node reported.
The load bars change color as they climb — blue under moderate load, yellow from about 75%, and red from about 90%. A card whose CPU or Egress bar sits in the red is a candidate for draining or for adding capacity.

Cached Resources

The final card is a searchable table of the resources present or active on each CDN server. Its columns are:

  • Server — the node holding the resource, with its number.
  • Resource — the resource identifier.
  • Protocol — the delivery protocol of the cached object.
  • State — the cache state, shown as a colored badge: active, complete, filling, queued, partial, cached, evicting or failed.
  • Users — viewers currently using the resource on that node.
  • Objects — the number of cached objects for the resource.
  • Cached — how much is cached out of the total size.
  • Progress — a bar showing how much of the resource is filled.
  • Upstream — the server the node pulls from, with the origin server noted.
  • Last Client Access — when a client last used the resource (internal CDN pulls are excluded).
  • Cache Updated — the newest local file time for the resource. This is the settings column at the end of the row.
The resource count badge reads, for example, 1 resource or 14 resources, and the table shows No CDN server data when nothing is reporting. For how the CDN assigns sessions and scores nodes, see the related articles below.

Related


Was this answer helpful?

« Back