Überwachen benutzerdefinierter Aktionen reporting

Weitere Informationen zu KPIs für benutzerdefinierte Aktionen

• Erfolgreiche Aufrufe: Gesamtzahl der HTTP-Aufrufe, die eine gültige Antwort ohne Fehler zurückgegeben haben.

• 4xx/5xx-Fehler: Anzahl fehlgeschlagener Aufrufe aufgrund von Client-seitigen (4xx) oder Server-seitigen (5xx) Fehlern, wobei Konfigurationsprobleme oder Endpunktfehler hervorgehoben werden.

• Timeouts: Anzahl der Aufrufe, die fehlgeschlagen sind, weil sie die maximale Antwortzeit überschritten haben. Dies hilft bei der Ermittlung von Latenz- oder Leistungsproblemen mit externen Endpunkten.

• Begrenzte Aufrufe: Anzahl der Aufrufe, die aufgrund von Begrenzungen blockiert wurden, um sicherzustellen, dass nachgelagerte Systeme nicht überlastet werden.

• Durchschnittliche RPS: Anzahl der Anfragen pro Sekunde, die von der benutzerdefinierten Aktion über den ausgewählten Zeitraum verarbeitet wurden.

• Durchschnittliche Latenz: Durchschnittliche End-to-End-Antwortzeit (in Millisekunden) für alle HTTP-Aufrufe, einschließlich erfolgreicher Aufrufe, Fehler und Zeitüberschreitungen.

• Durchschnittliche erfolgreiche Latenz: Durchschnittliche End-to-End-Antwortzeit (in Millisekunden) nur für erfolgreiche Aufrufe, ohne fehlgeschlagene Anfragen und Zeitüberschreitungen.

• Durchschnittliche Warteschlangenzeit: Durchschnittliche Zeit (in Millisekunden), die Aufrufe vor dem Senden in der Ausführungswarteschlange verbracht haben. Dies gilt nur für gedrosselte Endpunkte, bei denen Journey Optimizer Aufrufe in die Warteschlange stellt, wenn das Durchsatz-Limit erreicht ist.

Video ansehen

embed
https://video.tv.adobe.com/v/3479550?captions=ger&quality=12&learn=on

AI Knowledge Reference

This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.

For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.

• TL;DR: This page explains how to use the Custom action reporting page to monitor the reliability and performance of the API calls your journeys make to third-party systems.

Intents:

• Access the Custom action reporting page from the Actions homepage
• Review the Custom action KPIs for operational health and reliability
• Track HTTP call KPI trends over time with the Calls over time graph
• Analyze latency patterns with the Latency over time graph
• Drill into metrics per endpoint, custom action, and journey with the breakdown tables

Glossary:

• Custom action reporting page: The reporting page that lets you monitor the reliability and performance of API calls made from your journeys to third-party systems; it functions like other All-time reports (product-specific)
• Capped calls: Number of calls that were blocked due to capping limits, ensuring downstream systems are not overloaded (product-specific)
• Average queue time: Average time (in milliseconds) calls spent waiting in the execution queue before being sent (product-specific)
• Calls breakdown: A hierarchical table breaking metrics down from per endpoint, to per Custom Action using each endpoint, to the journeys that rely on them (product-specific)

Guardrails:

• Average queue time only applies to throttled endpoints, where Journey Optimizer queues up calls when the throughput limit is reached.
• Average latency covers all HTTP calls, including successful calls, errors, and timeouts, while Average successful latency covers successful calls only, excluding failed requests and timeouts.
• The granularity of the Calls over time series depends on the selected time range: a 7 day report shows KPIs per day, a 1-day time range shows KPIs per hour, and a 1-hour time range shows KPIs per minute.

Terminology:

• Canonical name: Custom action reporting page — Acronym: n/a — variants: Custom action report
• Synonyms: “Average RPS” = “requests per second processed by the custom action over the selected time range”
• Do not confuse: “4xx/5xx errors” (failed calls due to client-side or server-side errors) ≠ “Timeouts” (calls that exceeded the maximum response time) ≠ “Capped calls” (calls blocked due to capping limits)
• Do not confuse: “Average latency” (all HTTP calls) ≠ “Average successful latency” (successful calls only)

FAQ:

• Q: What does the Custom action reporting page monitor? — It monitors the reliability and performance of API calls made from your journeys to third-party systems, helping you identify integration issues, latency bottlenecks, or throttling and capping limits.
• Q: How do I access the Custom action reporting page? — Click the Monitoring icon from your Actions homepage.
• Q: What is the difference between Average latency and Average successful latency? — Average latency is the average response time for all HTTP calls including successful calls, errors, and timeouts, while Average successful latency is for successful calls only, excluding failed requests and timeouts.
• Q: When does Average queue time apply? — It only applies to throttled endpoints, where Journey Optimizer queues up calls when the throughput limit is reached.
• Q: Can I report on custom action performance outside this page? — Yes, you can use Adobe Experience Platform Query Service to build queries on custom action performance metrics.