Monitoring and Troubleshooting

monitoring viewing switches in zen master when zen master communication is configured, all switches will be reported to and reflected in zen master the target will show the proper channel and the switch will be reflected in the change log and event logs esam change tracking sample viewing switches on the broadcaster logs for the broadcaster can be found in the event log tab by searching “switch” in the log files the broadcaster produces, filtering for “switch” will also show the logs for switches requested event log messages message description switch source for output zen push oxwzpyvr rpvyweyr to wbd nba 001 fo west sxxd1q5 pm requested pts=8288264131 timed out switching anyway the provided pts was not found after the timeout, but the switch was done anyway if seamless is configured, a seamless switch was tried , then an immediate switch switch source for output zen push oxwzpyvr rpvyweyr to wbd nba file 001 fo west se21ryl pm requested pts=7695381841 detected pts=7697004962 diff=1623121 the provided pts was found and a switch was done on that pts scte 35 reporting when using the esam agent, all scte 35 messages seen on inputs on the broadcaster are still forwarded to zen master or any other external system the agent gets the url to post the scte 35 messages to from the scte 35 reports url defined in the broadcaster settings for example https //zen zixi com/reporting/broadcasters/xrpkpnqo/scte35 https //zen zixi com/reporting/broadcasters/xrpkpnqo/scte35 the agent updates the value on the broadcaster with a passthrough parameter that is the original reporting url and passes all scte that it receives on to the scte logging platform for example http //127 0 0 1 5555/signal?agentesam=1\&passthrough=https%3a%2f%2fzen zixi com%2freporting%2fbroadcasters%2fxrpkpnqo%2fscte35 http //127 0 0 1 5555/signal?agentesam=1\&passthrough=https%3a%2f%2fzen zixi com%2freporting%2fbroadcasters%2fxrpkpnqo%2fscte35 this process uses zen master api key authentication with the key in the headers x api key api key from zen master account scte 35 reports format the scte 35 information is reported in an http post and the data sent in the parameters parameter description stream streamid of input scte cmd binary of scte 35 message duration duration of break eventid id of the message programid id of the break pts pts time of splice point outofnetwork 1/0 if going in or out of network autoreturn 1/0 should the break close automatically immideate 1/0 if the break should be spliced immediately (it is spelled wrong) pts adjustment value the pts should be adjusted by pid the pid the scte 35 was captured on reporttime timestamp when scte 35 message was captured wallclocktime splice time converted to timestamp based on wall clock time sendtime timestamp when scte 35 report was sent to log scte in zen master, enable logging in the broadcaster cluster & source settings broadcaster clusters – scte 35 logging must be enabled if you wish to view scte 35 messages in zen master on each source or in the general logging page individual sources – scte 35 logging must be enabled on each source if you wish to view scte 35 messages for each input on the broadcaster troubleshooting the esam agent is very lightweight and stateless so restarts will not affect there are also debug logs to assist in deep diving were problems to arise when working through issues the best places to investigate are esam agent logs – found in the directory configured by the ‘logger’ section within the config file full logging details broadcaster logs – event logs, system logs, or log files zen master events – on the target or general logs sds logs – the external sds system