Procore Integration Health Observability

Overview

Combine provider-side observations with application-side service signals. Procore's Integration Health and API Call Activity Report identify unhealthy response patterns and routes, while the integration must supply latency, backlog, freshness, reconciliation, and release context.

Prerequisites

• App owner with Developer Portal access and a recurring review cadence
• Normalized route, status, latency, retry, queue, webhook, and freshness telemetry
• Release identifiers, endpoint owners, alert destinations, and incident runbook

Instructions

Step 1: Export provider evidence

Review Integration Health and download the production API activity report. Preserve report time range, app identity, and a checksum in the audit receipt.

Step 2: Join route ownership