Configuration and control options for Nimble Streamer
Nimble Streamer can be easily configured and controlled.
WMSPanel web interface
The best way to control and monitor Nimble Streamer instance is WMSPanel - a web service to control and report your servers.
- WMSPanel web UI is available via any browser.
- Multiple servers can be controlled via singe UI.
- Every setting can be applied to multiple servers within a few clicks simultaneously.
- You can grant permission to non-admin users to control particular Nimble Streamer instances.
Reporting. WMSPanel has an excellent reporting feature set which covers every aspect of streaming process and gives detailed metrics of your audience. It also allows setting up white label of your stats to represent them to your customers. Visit reporting section of our website to learn more.
Server console tasks. WMSPanel allows setting up server-side streaming tasks via Nimble Streamer with no need to log in via SSH.
This can include any stream processing as well as streaming environment setup, like running ffmpeg commands.
There are two config files for Nimble Streamer, each responsible for certain aspects of behavior.
nimble.conf is a configuration file which contains general settings which affect overall behavior.
Those settings can be typically defined only in this config file, not in web UI.
Check configuration parameters reference to see what may be interesting for you.
rules.conf is a file where you can specify server behavior related to protocols, applications, streams and their parameters.
Settings from WMSPanel override settings which were manually added to rules.conf, this is why this file is typically used in case someone cannot have control via web UI, e.g. in private networks.
The rules.conf syntax is being continuously changed for new features and interoperability improvements, so we have neither a reference nor a spec for it. Usually customers use WMSPanel to configure some accessible Nimble instance and them move its specs to private entities.
If you use WMSPanel to configure your servers, you don't need to touch this file.
Manual operation via WMSPanel web UI or configs are not the only ways to control live streaming behavior and get statistics.
HTTP APIs give more flexibility.
- WMSPanel API allows controlling servers' settings and get statistics from WMSPanel.
- Nimble Streamer native API allows getting real-time streams' status and performing some control activities on individual server instance, without interacting with WMSPanel.
Push APIs provide interactions between Nimble Streamer instance and handler applications on your side.
- Publish control framework allows to secure your ingest points from unwanted streams. It has several levels of control including custom handler web app to apply your business logic to your broadcasting process. This is especially useful for mobile broadcasting.
Read this overview to learn more about benefits of publish control framework and check the detailed setup description.
- Playback sessions authorization supports sessions authorization via external handler to decide which of the connecting users may continue receiving the stream.
- Pay-per-view framework is part of paywall framework which allows controlling playback on a particular stream or even single user level.
- Stream availability push API allows getting notifications about incoming publishing and un-publishing of RTMP, RTSP, MPEGTS, Icecast and Transcoder output streams.
Nimble Streamer is the most efficient software media server on the market which our customers use in various cases like utilizing 10Gbps bandwidth and low latency streaming.
Nimble can be adjusted and improved to handle huge amounts of viewers.
Take a look at performance tuning basics to learn about basic approaches to best performance.
Load balancing based on Nimble Streamer API can also be used to build scalable streaming.
Nimble supports server-side logging for further analysis.
Server logging article shows basic logging setup.
Configuration parameters reference provides full list of parameters to control logging under "Logging" label.