Hi, I’m John Viray on the Adobe product team. In this video, I’m going to show how monitoring can help you understand the general usage and endpoint errors in event forwarding properties. By the end of this video, you’ll be able to first, understand the number of incoming and outgoing calls to and from event forwarding. And second, know the number of errors across all properties and even run a query to understand the errors observed from a specific end point, With that, let’s jump into the product. After you select monitoring from the left rail navigation, you’re brought to this screen. Monitoring includes three reports, usage, error events and compute time, The property and environment selector above the usage report controls all three of the reports to make sure the reports are viewed within the same context. The usage report shows a total number of incoming and outgoing calls for a given month. Error events shows the errors observed from endpoints being hit from event forwarding. You can also choose from several different timeframes. Hover over the line graph to see the breakdown of endpoint error response codes and even enter the domain of an endpoint to see how many errors are observed from that particular endpoint. Right now, this query must be an exact match. For example, to see how many errors are reported from the Facebook conversions API, I would enter the end point domain and press Enter. Lastly is compute time. This report does not show end to end latency. It shows the actual time it takes to execute all the rules in the event forwarding property. This compute time excludes any idle time event forwarding spends waiting for an endpoint to respond. We included this data because there is a 50 millisecond limit. However, in all our observations, we haven’t seen any customer come remotely close to this threshold. This wraps up the overview of monitoring and we hope you enjoy the first iteration of this feature. -