사용자 정의 액션 모니터링 reporting

사용자 지정 작업 KPI에 대해 자세히 알아보기

• 성공한 호출: 오류 없이 유효한 응답을 반환하는 총 HTTP 호출 수입니다.

• 4xx/5xx 오류: 클라이언트측(4xx) 또는 서버측(5xx) 오류로 인해 실패한 호출 수로, 구성 문제 또는 끝점 오류가 강조 표시됩니다.

• 시간 초과: 최대 응답 시간을 초과하여 실패한 호출 수입니다. 이렇게 하면 외부 끝점과 관련하여 지연 또는 성능 문제를 표면화하는 데 도움이 됩니다.

• 제한된 호출: 제한 제한으로 인해 차단된 호출 수로 다운스트림 시스템이 오버로드되지 않도록 합니다.

• 평균 RPS: 선택한 시간 범위 동안 사용자 지정 작업에서 처리한 초당 요청 수입니다.

• 평균 대기 시간: 성공한 호출, 오류 및 시간 제한을 포함하여 모든 HTTP 호출에 대한 평균 종단 간 응답 시간(밀리초)입니다.

• 성공한 평균 대기 시간: 실패한 요청 및 시간 초과를 제외하고 성공한 호출에 대해서만 평균 전체 응답 시간(밀리초)입니다.

• 평균 큐 시간: 전송하기 전에 실행 큐에서 대기하는 데 걸린 평균 시간(밀리초)입니다. 이는 처리량 제한에 도달했을 때 Journey Optimizer이 호출을 큐에 추가하는 제한된 끝점에만 적용됩니다.

비디오 보기

embed
https://video.tv.adobe.com/v/3479548?captions=kor&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.