Monitor your custom actions

Transcript

Hi everyone, this is a quick demo of the Custom Action Monitoring report. This report allows you to monitor the operational health and performance of HTTP calls made from your journeys to third-party endpoints via Custom Actions. This report will help you quickly identify HTTP errors, latency bottlenecks, and capping issues that may impact delivery. The goal is to give you better visibility into Custom Action Health and empower you to address issues that may arise. Let’s jump into the product.

From the AGO homepage, we click on Configurations and then on Actions.

Then we click on this little icon in the upper right-hand corner. I’ve preloaded it in this tab. This is the Custom Action Monitoring report. Let’s walk through a couple of key areas. Here at the top, we have some high-level KPIs, successful calls, client and server errors, timeouts, capped calls, throughput, and latency metrics. A blank field indicates a value of zero.

Following that, we have calls over time where you can see various metrics over a time period that you select. We’re currently looking at the last seven days. This view changes based on the specific metrics selected in the breakdown table below. We’ll get to that shortly.

Latency over time provides a similar view, but for the latency metrics.

Next, we have a breakdown of Custom Action metrics in a specific hierarchy. The top level is the endpoint that the Custom Action is calling. Next is the Custom Action itself. Following that are the journeys that are using that Custom Action to call that endpoint. For example, if I go down to this third endpoint, you can see that it is being called by a single Custom Action and that we have several journeys that are utilizing that Custom Action. At the journey level, you can see that this journey has had 80 successful calls, 55 400-level errors, 10 500-level errors, 38 timeouts, and 46 requests per second.

Now, if I click on a cell or row in the table, I will see the calls over time chart update to display only the data I care about.

The latency table follows a similar hierarchy broken down by endpoint, Custom Action, and journey.

Lastly, we have the Insights Builder where you can create your own custom visualizations. For example, if I wanted to look at Custom Action 400 and 500-level errors, I can.

You can build your own visualizations based on the metrics you’d like to look at. Lastly, here on the left-hand side, there’s a table of contents where you can quickly navigate to sections of the report you care about. Thank you for watching.