Webhook instrumentation

Choose a boundary

Instrument the handler that owns the business operation.

Wrap the handler that converts a provider event into an application result. One stable route template and Integration key should describe that external workflow.

Preserve behavior

Keep the existing result and error authoritative.

observeWebhook invokes the existing handler and records its accepted result or error after the operation. Do not replace provider acknowledgement, retry, or idempotency logic with collector behavior.

Route templates

Use stable templates instead of high-cardinality URLs.

• Use /webhooks/candidate, not /webhooks/candidate/123.
• Keep customer IDs out of route metadata.
• Use eventType for low-cardinality provider event names.