Streamer management¶

Streamers in Agora are execution nodes that handle ingest, publication, hardware devices, and operational telemetry. Managing them connects real servers to the platform, tracks their health, and uses them in streams and IO devices.

From the streamers section an administrator can:

• register origin and edge servers;
• set how the controller connects to them;
• monitor load and health;
• prepare the environment for streams and IO devices.

Streamer list¶

The list shows every registered node. Per streamer you see:

• hostname;
• running vs. configured stream counts;
• connected client count;
• CPU load;
• disk usage.

From the list you can:

• open a streamer card;
• add a streamer;
• refresh manually.

This screen is a quick health view of Agora infrastructure nodes.

Creating a streamer¶

To create a streamer in the current UI you only need:

• hostname.

After creation the streamer gets an internal ID and can be configured further.

Streamer card¶

In the streamer card an administrator can:

• change hostname;
• choose connection scheme: HTTP or HTTPS;
• set the API port;
• configure config_api_key;
• configure edit_auth;
• save changes;
• reload streamer data;
• delete the streamer.

If there are unsaved edits, the UI warns before navigating away.

Connection parameters¶

Remote access is defined by:

• HTTP / HTTPS scheme;
• API port;
• config_api_key for external configuration access;
• edit_auth for edit operations.

These control how the controller talks to the streamer.

config_api_key lets the streamer use config_external and receive full server configuration from the controller — it acts as the password for centralized configuration.

Working with secrets¶

Secret fields support:

• show/hide value;
• copy config_api_key;
• generate a new config_api_key.

That simplifies bootstrap and key rotation.

curl command for external configuration¶

For an existing streamer the UI can show a ready-made curl command for the external configuration endpoint.

It helps:

• see which config the streamer will receive;
• verify the configuration URL;
• confirm config_api_key is correct.

Relations to other areas¶

Configured streamers are used when:

• binding IO devices;
• configuring HDMI / SDI hardware capture;
• designing clustered ingest and publication;
• monitoring infrastructure health.