Monitoring integration performance with Event Monitoring
Matching each integration symptom to the monitoring source that measures it: Apex Jobs and AsyncApexJob for queued work, API usage notifications and the Limits resource for allocation, the Concurrent Long-Running Apex Limit, Apex Callout, REST API and Bulk API 2.0 event log files for duration, PlatformEventUsageMetric for event delivery, and hourly versus daily log files.
Given an integration maintenance use case, identify performance monitoring needs for integration requirements.
~8 min read · 8 practice questions ·
What the exam expects
- Pick the monitoring source that measures a stated integration symptom, and reject sources that measure something else (inbound vs outbound, count vs duration, jobs vs events).
- Monitor queued and failed asynchronous Apex with the Apex Jobs page and
AsyncApexJob. - Alert on API consumption with API usage notifications, and track allocations with the REST Limits resource.
- Read the integration event log file types: Concurrent Long-Running Apex Limit, Apex Callout, REST API (
DB_TOTAL_TIMEvsCPU_TIME) and Bulk API 2.0. - Trend platform event and change event delivery with
PlatformEventUsageMetric, and choose hourly or daily log files.
Key terms: event log file (a CSV of one event type's activity, read through the EventLogFile object), interval (Hourly or Daily file schedule), allocation (the org's entitled usage per period), long-running request (synchronous Apex executing 5 seconds or more), delivery metric (events sent to external subscribers).
Key facts
- Detail
- Apex Jobs page or
AsyncApexJob(Status,NumberOfErrors)
- Detail
- Email past a % of allocation over set hours; up to 10 per org
- Detail
- Accurate within five minutes of consumption
- Detail
- 5 seconds; limit 1 per 100 licenses, min 10, max 50
- Detail
- HTTP callout processing time isn't counted toward that limit
- Detail
URL,TIME(ms),STATUS_CODE,SUCCESS
- Detail
- Compare
DB_TOTAL_TIMEwithCPU_TIME
- Detail
- Inbound SOAP, REST and Bulk API requests; no duration field
- Detail
- Separate platform and change event metrics; no trigger or flow deliveries
- Detail
numberRecordsFailed,totalProcessingTimefrom Get Job Info
- Detail
- 3-6 hours or longer; use daily files for complete data
Sources for this section (10)
- Queueable Apexdeveloper.salesforce.com (opens in a new tab)
- Manage API Usage Notificationshelp.salesforce.com (opens in a new tab)
- Limits (REST API)developer.salesforce.com (opens in a new tab)
- Execution Governors and Limitsdeveloper.salesforce.com (opens in a new tab)
- Apex Callout Event Typedeveloper.salesforce.com (opens in a new tab)
- REST API Event Typedeveloper.salesforce.com (opens in a new tab)
- API Total Usage Event Typedeveloper.salesforce.com (opens in a new tab)
- Monitor Platform Event Publishing and Delivery Usagedeveloper.salesforce.com (opens in a new tab)
- Get Information About an Ingest Jobdeveloper.salesforce.com (opens in a new tab)
- Using Event Monitoringdeveloper.salesforce.com (opens in a new tab)
- Why can't API Total Usage diagnose a slow outbound callout?
- When should you compare `DB_TOTAL_TIME` with `CPU_TIME`?
- Why pair `PlatformEventUsageMetric` with the Limits resource?
- What does a concurrent long-running Apex limit of 50 imply?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Integration Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 25 lessons of the Integration Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (8 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams