API Performance
API Performance is the technical health view of Connect: request volume, success and error rates, latency, and how failures cluster. Use it to find a degraded connection, then open Log & Audit for the matching operations.
Open: app.bundleport.com/connect/observability (connect.read). Alias: /connect/performance.
This screen is full volume (not the sampled audit grain).
Filters
- Date range
- Connection
- Environment: test, prod, or all
- Service: hotels, flights, ground, or all
- Operation tab: All, Search, Quote, Book, Cancel, Other
API health KPIs
- Total requests
- Success rate, error rate
- Average response time, P95 response time
Funnel KPIs
Always computed across methods (not only the selected operation tab): look-to-book (L2B), quote-to-book (Q2B), confirmation rate, cancellation rate.
Connections and operations
The connections table sets status from success rate only (UI, not an API field):
- Healthy: 98% or above
- Degraded: 95% up to but not including 98%
- Down: below 95%
The operations table breaks the same period by search / quote / book / cancel. Throughput is a time series. Top errors list descriptions. An error donut groups by error_category, and falls back to error_type when every category is unknown.
error_category (console only)
These buckets match the aggregator stats classifier. They are not a field on Hotels errors[]. Do not send them on the wire.
| Bucket | Typical description |
|---|---|
rate_limit | rate limit, 429, too many requests |
allotment | allotment |
timeout | timeout, timed out, deadline, did not respond within |
confirmation | booking confirmation error, please do not retry |
system_error | circuit breaker, connection refused, internal server error |
unknown | Everything else, including generic Response contains errors. |
Hotels still returns ERR_CODE_* / ERR_TYPE_* on HTTP 200. Follow additionalData.recommended_action when present. Catalog: Error codes.
Drill-downs from this page open Log & Audit with the same connection, time range, and error filters.