Origin mapping

Rob 2015-01-06 10:04:10 UTC in Nimble Streamer

Hi. In Nimble HLS edge restreaming setup...
1) it possible to map the incoming request to specific origin server based on some variable in incoming request?
2) in case of origin server failure is there a possibility to automatically failover to another origin server?

Yury Udovichenko 2015-01-06 10:59:55 UTC 

Hi Rob,

Thanks for the interest.

1. You may specify different application URLs which will be pointing to different servers in re-streaming routes.

2. This may be done if you use RTMP as an origin for further HLS transmuxing. You may specify multiple RTMP sources for failover:

Rob 2015-01-08 16:21:39 UTC 


1) To clarify that with an example:

- 5 origin servers (Custom)
- 5 edge servers (Nimble)

Incoming requests to edge server:

should be mapped to


How can we archive that?

2) In our case it's HLS on origin

Yury Udovichenko 2015-01-09 03:09:56 UTC 

The failover for re-streaming scenario now seems clear and I think it's a good one to implement in one of the next releases, thanks for the idea.

As for switching among origins, this already can be done via setting up different routes for different origins. So the routes for 2 origins and 2 edges would be:
origin1/live/ -> /o1/live applied for edge1 and edge2
origin2/live/ -> /o2/live applied for edge1 and edge2
You can send me an email at with examples of your origin streams so I could make sample routes for you.

Post a reply

Post a new question


This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the Privacy Policy. If you want to know more or withdraw your consent to all or some of the cookies, please refer to the Privacy Policy.
By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies.