Pull Monitoring

Why You Would Use This

Pull endpoint monitoring gives you visibility into what events are being received and how quickly they are being processed. Use logs to inspect individual events across endpoints, and metrics to track ingestion volume, fetch rates, and acknowledgment rates.

Console Workflow

1. Open a pull endpoint to view stored, fetched, and delivered event counts.
2. Use the events table filters to browse events by status, event type, or date range.
3. Check the dashboard for pull endpoint metrics.

API Workflow

API reference:

• Get pull logs
• Get pull metrics
• Get pull time-series metrics

Pull logs

View events across all pull endpoints in your project:

# Recent events across all pull endpoints
curl "https://api.hookbridge.io/v1/pull-logs?limit=50" \
  -H "Authorization: Bearer YOUR_API_KEY"

# Filter to a specific endpoint
curl "https://api.hookbridge.io/v1/pull-logs?pull_endpoint_id=YOUR_PULL_ENDPOINT_ID&limit=50" \
  -H "Authorization: Bearer YOUR_API_KEY"

# Filter by status and event type (status: stored, fetched, or delivered)
curl "https://api.hookbridge.io/v1/pull-logs?status=stored&event_type=order.created&limit=50" \
  -H "Authorization: Bearer YOUR_API_KEY"

# Filter by time range
curl "https://api.hookbridge.io/v1/pull-logs?start_time=2026-03-01T00:00:00Z&end_time=2026-03-02T00:00:00Z" \
  -H "Authorization: Bearer YOUR_API_KEY"

Pull metrics

Get aggregated metrics for a time window:

# Metrics for the last 24 hours
curl "https://api.hookbridge.io/v1/pull-metrics?window=24h" \
  -H "Authorization: Bearer YOUR_API_KEY"

# Metrics for a specific endpoint over the last 7 days
curl "https://api.hookbridge.io/v1/pull-metrics?window=7d&pull_endpoint_id=YOUR_PULL_ENDPOINT_ID" \
  -H "Authorization: Bearer YOUR_API_KEY"

Available windows: 1h, 24h, 7d, 30d.

Time-series metrics

Get metrics broken into time buckets for charting:

curl "https://api.hookbridge.io/v1/pull-metrics/timeseries?window=24h&pull_endpoint_id=YOUR_PULL_ENDPOINT_ID" \
  -H "Authorization: Bearer YOUR_API_KEY"

Bucket size varies by window: 1-minute buckets for 1h, 15-minute for 24h, 2-hour for 7d, 12-hour for 30d.

Recommended Runbook Pattern

1. Check pull metrics to confirm ingestion volume is within expected range.
2. If stored event count is growing, check whether your consumer is running and fetching events.
3. If fetched event count is growing but delivered count is flat, your consumer is retrieving events but failing to acknowledge them. Check for processing errors or crashes between fetch and ack.
4. Use pull logs filtered by status=stored or status=fetched to identify unprocessed events.
5. Use event type filters to isolate specific provider event streams.
6. If events are arriving but with null event types, review your event type extraction config.