---
title: Monitoring and Troubleshooting
slug: market-switching/monitoring-and-troubleshooting
docTags: 
createdAt: 2025-05-27T19:32:19.595Z
---

## 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](https://api.archbee.com/api/optimize/amUtKWPrNQCS-26DKyGuI-ztido7fLZoE9ZbrnV3wh4-20250527-183503.png "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: 

1. 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 
2. 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