Adding HTTP Targets

zen master supports six types of http targets http – the channel is pushed to any http server via http put methods this option also includes the ability to use secure https protocol youtube the channel is pushed to youtube s3 bucket – the channel is pushed to an aws s3 storage service mediastore the channel is pushed to an aws elemental mediastore storage service gcp storage – the channel is pushed to a google gcp storage service azure – the channel is pushed to azure blob storage as part of the target configuration, you will assign the target to an existing channel, as the target will only become functional once a channel is attached to it however, it is possible to add a channel to a target after the initial configuration the selected channel has been configured to provision the egress cluster (processing cluster setting) and the specific broadcaster/s within this cluster (target broadcaster/s setting) the following procedure describes how to add an http target in zen master in addition, an explanation of each of the configuration parameters is given in the table below to add a new http target in the main navigation, click targets click + add the create new target window is displayed click on http the create new http target window is displayed in the info section, in the name field, enter a logical name for the http target in the tags field, select one or more of the predefined tags from the drop down list tags are used for access control by selecting a tag you are relating this target to that tag tags are associated with certain roles (through the users & roles screen), and roles, in turn, are associated with users and user groups if you would like to create a new tag, see docid\ ypm9tw81ap6nq8stkv4rd in the events configuration profile field, select from the dropdown list the profile that you would like to apply to this target by default, the default profile is applied events profiles consist of a series of rules that determine precisely how various types of events are logged and what results they trigger the target's location is used to represent it in the proper position in the map display (see docid\ sfzm6jvorvuigo7x0dnue ) by default, the location is determined automatically based on the target's ip if you would like to manually set the location of the target (optional), use the following procedure click on the edit icon next to the location field a search box is shown below the location field enter identifying info for the location (e g street address, zip code, coordinates) search results are displayed below the search box as you type click on the desired location the selected location populates the location field in the configuration section, in the channel field, select from the drop down list the channel that will be sent to the target (optional field) the target will only become functional once a channel has been assigned to it however, you can configure the target settings and then add a channel to the target after the initial configuration in the type field, select one of the following options azure – the channel is pushed to azure blob storage gcp storage the channel is sent to a gcp storage service http – the channel is sent to an http server mediastore – the channel is pushed to an aws elemental mediastore storage service s3 bucket – the channel is sent to an aws s3 bucket storage service tams the channel is sent to a docid\ xb6n9zunccgoddabrvsba repository youtube – the channel is sent to youtube enter the required information for the selected target type as follows for target type http – in the encapsulation section, select the type of encapsulation used, options are hls or cmaf ( dash + fmp4 hls) in the ingest url field, enter the ingest url of the http server to which the channel will be pushed for target type tams in the tams api url field, enter the url for api access to your tams instance check ignore certificate if you don't want sending streams because a certificate is faulty or not detected enter the oauth client id that is used to authenticate api requests to tams enter the oauth secret key that is used to authenticate api requests to tams enter the authorization token url used to retrieve authorization tokens for target type youtube – in the encapsulation section, select hls in the ingest url field, enter the ingest url provided by youtube to which the channel will be pushed in the youtube stream key field, enter the stream key that is provided by youtube for target type s3 storage – in the encapsulation section, select the type of encapsulation used, options are hls or cmaf (dash + fmp4 hls) in the s3 uri field, enter the uri of the s3 bucket in the region field, select from the drop down list the aws region of the s3 bucket in the access key id field, enter the access key id used to access your aws account in the secret access key field, enter the secret access key used to access your aws account for target type mediastore – in the encapsulation section, select the type of encapsulation used, options are hls or cmaf (dash + fmp4 hls) in the mediastore uri field, enter the uri of your mediastore storage service in the region field, select from the drop down list the aws region of your storage service in the access key id field, enter the access key id for your mediastore account in the secret access key field, enter the secret access key id for your mediastore account for target type gcp – in the encapsulation section, select the type of encapsulation used, options are hls or cmaf (dash + fmp4 hls) in the gcp account field, select an account from the drop down list in the ingest url field, enter the ingest url of the gcp storage service to which the channel will be pushed for target type azure – in the encapsulation section, select the type of encapsulation used, options are hls or cmaf (dash + fmp4 hls) in the azure account field, select a linked account from the drop down list in the ingest url field, enter the ingest url of the azure storage service to which the channel will be pushed in the playback url field, enter an alternative url for playback and hls validation for an s3 bucket target this field is optional, if no url is entered then zen master will use the url of the s3 bucket for playback and validation for an http server target zen master will not validate the stream or enable playback unless a url is entered in this field select the upload dvr playlist checkbox if you are streaming a recorded/vod stream and you want to upload a dvr playlist in addition to the live playlist select the delete outdated checkbox if you would like zen master to delete any outdated fragments from the server (default selected) in the propagate tags to s3/mediastore objects , select this checkbox if you want zen master to create aws backend tags for the tags, which were assigned to this hls target, and propagate them to s3 and/or mediastore objects these tags will be applied to the manifest, the chunks, and folders select the ignore certificate checkbox if you are sending the stream to a trusted server which does not have a valid certificate when this option is selected, the zixi broadcaster will ignore tls certificate errors and send the stream to its destination if you would like to receive alerts for subtitles missing from the stream, select the alert on missing webvtt captions checkbox and then in the search window field, enter the number of seconds of missing subtitles to generate the alert (default 30 seconds) in the initial state section, select the disabled checkbox if you would like to disable this target upon initial configuration select the muted checkbox if you would like to disable error/recovery notifications for this target upon initial configuration you canin the protections field, enable/unmute the target at any time under protections , select the channel reassignment protection chekbox if you want to prevent the reasssignment of this target to another channel this is helpful in cases where you are switching the channel on multiple targets at once and can accidetaly select a target that should not have been switched to the new channel if you would like to configure advanced settings, click on advanced and enter values for the desired fields see the paramaters table below for explanations of the fields click save http target configuration parameters table parameter description info name specify a name for the http target in zen master tags select one or more of the predefined tags from the drop down list tags are used for access control by selecting a tag, you are relating this target to that tag tags are associated with certain roles (through the users & roles screen), and roles, in turn, are associated with users and user groups if you would like to create a new tag, see docid\ ypm9tw81ap6nq8stkv4rd events configuration profile select from the dropdown list the profile that you would like to apply to this target by default, the default profile is applied note events profiles consist of a series of rules that determine precisely how various types of events are logged and what results they trigger location (optional) the target's location is used to represent it in the proper position in the map display (see ) by default, the location is determined automatically based on the target's ip enter identifying info for the location (e g street address, zip code, coordinates) and select the desired location from the suggestions that are shown configuration channel (optional) select from the drop down list the channel that will be sent to the target type select one of the following options azure – the channel is pushed to azure blob storage gcp the channel is sent to a gcp storage service http – the channel is sent to an http server mediastore – the channel is pushed to an aws elemental mediastore storage service s3 bucket – the channel is sent to an aws s3 bucket storage service youtube the channel is sent to youtube for http type encapsulation select the type of encapsulation used options are hls or cmaf (dash + fmp4 hls) ingest url enter the ingest url of the http server to which the channel will be pushed for the tams type tams api url the url for api access to your tams instance ignore certificate check the box if you don't want sending streams because a certificate is faulty or not detected client id client id use to authenticate api requests to your tams instance secret key secret key use to authenticate api requests to your tams instance authorization token url url used to retrieve authorization tokens for your tams instance for youtube type encapsulation select the type of encapsulation used options are hls only ingest url enter the ingest url provided by youtube to which the channel will be pushed youtube stream key enter the stream key that is provided by youtube for s3 storage type encapsulation select the type of encapsulation used options are hls or cmaf (dash + fmp4 hls) s3 uri enter the uri of the s3 bucket region select from the drop down list the aws region of the s3 bucket access key id enter the access key id used to access your aws account secret access key enter the secret access key used to access your aws account propagate tags to s3/mediastore objects select this checkbox if you want zen master to create aws backend tags for the tags, which were assigned to this hls target, and propagate them to s3 and/or mediastore objects these tags will be applied to the manifest, the chunks, and folders for mediastore type encapsulation select the type of encapsulation used options are hls or cmaf (dash + fmp4 hls) mediastore uri enter the uri of your mediastore storage service region select from the drop down list the aws region of your storage service access key id enter the access key id for your mediastore account secret access key enter the secret access key id for your mediastore account propagate tags to s3/mediastore objects select this checkbox if you want zen master to create aws backend tags for the tags, which were assigned to this hls target, and propagate them to s3 and/or mediastore objects these tags will be applied to the manifest, the chunks, and folders for gcp type encapsulation select the type of encapsulation used options are hls or cmaf (dash + fmp4 hls) gcp account select an account from the drop down list note to connect a gcp account to zen master, see docid\ jbuzi2tjvsps3o vzvxxh ingest url enter the ingest url of the gcp storage service to which the channel will be pushed for azure type encapsulation select the type of encapsulation used options are hls or cmaf (dash + fmp4 hls) azure account select a linked account from the drop down list note to connect an azure account to zen master, see docid\ jsst1kxhrrrfcdyc1lenl ingest url enter the ingest url of the azure storage service to which the channel will be pushed for all types playback url enter an alternative url for playback and hls validation note for an s3 bucket target this field is optional, if no url is entered then zen master will use the url of the s3 bucket for playback and validation for an http server target zen master will not validate the stream or enable playback unless a url is entered in this field upload dvr playlist select this checkbox if you are streaming a recorded/vod stream and you want to upload a dvr playlist in addition to the live playlist delete outdated select this checkbox if you would like zen master to delete any outdated fragments from the server (default selected) ignore certificate select this checkbox if you are sending the stream to a trusted server which does not have a valid certificate when this option is selected, the zixi broadcaster will ignore tls certificate errors and send the stream to its destination alert on missing webvtt captions if you would like to receive alerts for subtitles missing from the stream, select this checkbox note even if this checkbox is not selected, zen master will monitor the subtitles and validate them with the stream, but you will not receive notifications for missing subtitles initial state disabled select this checkbox if you would like to disable this target upon initial configuration muted select this checkbox if you would like to disable error/recovery notifications for this target upon initial configuration protections channel reassignment protection select this option if you want to prevent the reasssignment of this target to another channel this is helpful in cases where you are switching the channel on multiple targets at once and can accidetaly select a target that should not have been switched to the new channel advanced billing code if you would like to track usage for this target, enter your billing code details, see (supported for broadcasters v14 8+) billing password enter the password that corresponds to this billing code segment path select one of the following path segmentation types full path – in this option the path would be constructed as follows \<base url>/\<path>/\<file>?\<additional params may be also with path and file> path in parameters in this option the path would be constructed as follows \<base url>?\<additional params may be also with path and file> flat path in this option the path would be constructed as follows \<base url>/\<path> \<file>?\<additional params may be also with path and file> any "/" in path should be replaced with " " upload type (for cmaf encapsulation) select the specific type dash dash & fmp4 hls fmp4 hls