← Back to documentation

Observability

Track endpoint health with Activity charts, outcome filters, and log analysis.

8 min read

Use Request activity to detect failures quickly and confirm fixes.

Purpose

This guide helps you:

  • Read request volume trends.
  • Investigate request outcomes and error reasons.
  • Isolate endpoint-specific problems.

Prerequisites and permissions

  • Signed-in access to Request activity.
  • At least one endpoint receiving traffic.

Step-by-step workflow

1. Open Request activity

The page has two views:

  • Volume Chart
  • Request Log

Both support endpoint filtering.

2. Analyze request volume

In Volume Chart:

  1. Choose endpoint (All endpoints or one endpoint).
  2. Choose window (Month, Week, Day).
  3. Navigate previous/next windows.
  4. Review total, average, and peak counts.

UI cue: chart labels and summary metrics update immediately when endpoint/window changes.

3. Investigate request outcomes

In Request Log:

  • Use outcome filters (All, Success, Errors, Test).
  • Review Outcome and Error reason columns.
  • Page through results for large datasets.

Current outcomes:

  • ACCEPTED
  • AUTH_FAILED
  • CAPTCHA_FAILED
  • DELIVERY_FAILED
  • DISABLED
  • FIELD_VALIDATION_FAILED
  • MISSING_REQUIRED_HEADERS
  • METHOD_NOT_ALLOWED
  • TEST_ACCEPTED
  • TEST_REJECTED
  • TEST_RATE_LIMITED

4. Drill down by endpoint

  1. Filter to one endpoint.
  2. Compare outcomes against endpoint settings (method, auth, captcha, validation, outputs).
  3. Use trend direction to confirm recovery after changes.

Expected result and verification checks

  • You can distinguish input rejection vs destination-delivery failures.
  • You can scope incidents to one endpoint, one provider, or broader impact.

Data retention and privacy:

  • Activity data is retained for 30 days.
  • Request payload bodies are not stored.

Common issues and fixes

  • Traffic drops to zero: verify sender integration and endpoint URL.
  • METHOD_NOT_ALLOWED spikes: sender method drifted from endpoint setting.
  • DELIVERY_FAILED spikes: inspect relay target auth/URL/TLS and destination uptime.

Related guides

← Back to documentation