API Gateway Traffic Logging and Monitoring

We've seen projects where production starts returning 500s due to a single endpoint overload, and developers spend hours searching through scattered logs for the cause. Without a central entry point—a gateway—you're blind: you can't see who's calling the API, with what latency, which routes are failing. Configuring logging and traffic monitoring via an API Gateway solves these problems in a couple of days and gives full traffic transparency. Our 10+ years of experience implementing such solutions ensures stability and reduces incident investigation time to 15 minutes—an 87.5% reduction.

We integrate the collection of minimal necessary fields into your gateway: request_id (distributed tracing), consumer_id (client identification), method, path, status_code, latency_ms, request/response sizes. We don't log the request body by default—only in debug mode for selected routes to avoid exposing sensitive data. After implementation, one team cut their incident investigation time from 2 hours to 15 minutes, saving $50,000 per year in engineering hours.

Which metrics are critical for API debugging?

Without centralized collection, you can't quickly answer: which endpoint is the slowest, who generates 90% of errors, why did the upstream fail. We configure the gateway so every request leaves a complete digital trace:

Each request is also enriched with labels (consumer, route)—enabling slices by client and endpoint.

Risks of logging the request body

In production, the request body contains sensitive data: passwords, tokens, PAN data. We configure the gateway so that the body is logged only for selected routes in debug mode. In Kong this is controlled by the dataTraceEnabled flag, in AWS by a separate config. If a specific request needs debugging, we enable body logging for 15 minutes and then disable it. Kong documentation recommends enabling body logging only when necessary to avoid data leaks. Kong documentation

How distributed tracing works with request_id

request_id is a UUID generated at the gateway and passed to all backend services via the HTTP header X-Request-ID. Each service records its own unique request identifier in logs, allowing a complete picture of a single request execution. To achieve this, simply add the header to all outgoing calls—this is done with middleware in an hour. After that, you can build a "request path" dashboard showing all inter-service calls.

How to configure Kong Gateway for metric collection

Kong is the most popular self-hosted gateway. Logging via the http-log plugin and metrics via prometheus are configured in one config:

plugins:
  - name: http-log
    config:
      http_endpoint: http://logstash:5044/kong
      method: POST
      timeout: 1000
      keepalive: 1000
      flush_timeout: 2
      retry_count: 10
      queue:
        max_batch_size: 200
        max_coalescing_delay: 1
        max_entries: 10000
  - name: prometheus
    config:
      per_consumer: true
      status_code_metrics: true
      latency_metrics: true
      bandwidth_metrics: true
      upstream_health_metrics: true

After that, /metrics on Kong Manager returns all metrics in Prometheus format. Scrape interval: 15 seconds.

Configuration in AWS API Gateway

In AWS, logging is configured at the Stage level via CloudWatch:

{
  "loggingLevel": "INFO",
  "dataTraceEnabled": false,
  "metricsEnabled": true,
  "accessLogDestinationArn": "arn:aws:logs:us-east-1:123456789:log-group:api-gateway-access",
  "accessLogFormat": "{\"requestId\":\"$context.requestId\",\"ip\":\"$context.identity.sourceIp\",\"caller\":\"$context.identity.caller\",\"user\":\"$context.identity.user\",\"requestTime\":\"$context.requestTime\",\"httpMethod\":\"$context.httpMethod\",\"resourcePath\":\"$context.resourcePath\",\"status\":\"$context.status\",\"protocol\":\"$context.protocol\",\"responseLength\":\"$context.responseLength\",\"integrationLatency\":\"$context.integrationLatency\",\"responseLatency\":\"$context.responseLatency\"}"
}

dataTraceEnabled: false—never enable in production, it logs request bodies.

CloudWatch Insights query for p95 latency by endpoint:

fields @timestamp, resourcePath, responseLatency
| filter status >= 200
| stats pct(responseLatency, 95) as p95 by resourcePath
| sort p95 desc
| limit 20

Nginx API Gateway + OpenTelemetry

If the gateway is on Nginx (nginx-plus or OpenResty), logging is configured via log_format:

log_format api_json escape=json
  '{'
    '"timestamp":"$time_iso8601",'
    '"request_id":"$request_id",'
    '"method":"$request_method",'
    '"path":"$uri",'
    '"status":$status,'
    '"latency_ms":$request_time,'
    '"upstream_latency_ms":"$upstream_response_time",'
    '"bytes_sent":$bytes_sent,'
    '"consumer":"$http_x_consumer_id",'
    '"ip":"$remote_addr"'
  '}';

access_log /var/log/nginx/api_access.log api_json buffer=32k flush=5s;

For distributed tracing, use opentelemetry-nginx-module—we plug it in as needed.

Which visualization stack to choose: ELK or Grafana?

For most projects, Grafana Stack is easier to operate and 2-4 times cheaper than ELK. It also offers better integration with Prometheus and OpenTelemetry. ELK is justified when complex log searching is needed (incident analysis, retrospection). Using Loki instead of Elasticsearch can reduce storage costs by up to 75%.

Alerting

Minimum alert set (Prometheus AlertManager / Grafana Alerting) — Prometheus AlertManager is more efficient than traditional logging-based alerting for real-time metrics:

- alert: APIHighErrorRate
  expr: |
    sum(rate(kong_http_requests_total{status=~"5.."}[5m]))
    / sum(rate(kong_http_requests_total[5m])) > 0.05
  for: 2m
  labels:
    severity: critical
  annotations:
    summary: "Error rate > 5% over the last 5 minutes"

- alert: APIHighLatency
  expr: |
    histogram_quantile(0.95,
      sum(rate(kong_request_latency_ms_bucket[5m])) by (le, route)
    ) > 2000
  for: 5m
  labels:
    severity: warning
  annotations:
    summary: "p95 latency > 2s for route {{ $labels.route }}"

Work process and what's included in the result

1. Analytics: we study your API architecture, current gateways, traffic volume, storage requirements. We handle up to 100,000 req/s.
2. Design: choose the stack (Kong/AWS/Nginx), define logging schema, set retention to 30 days.
3. Implementation: deploy gateway with plugins, configure metric collection, connect Logstash/Loki. We guarantee configuration correctness.
4. Testing: verify log correctness, simulate errors, test alerts.
5. Deployment: publish configuration, train the team on dashboards.

In the end you get:

• Documentation on logging schema and fields.
• Dashboard access (Grafana/Kibana) for each team member.
• Configured alerts on critical metrics.
• Team training: how to read logs, how to respond to alerts.
• 2 weeks of support after launch.

Implementation timeline

Basic logging and dashboards: 2–3 days. Full stack with alerting, tracing, and retrospective analysis: 1–2 weeks depending on infrastructure maturity.

We'll assess your project and propose an optimal configuration in 1–2 days. Contact us for a gateway audit—we'll prepare the architecture and send an example configuration. Get a consultation on setting up your API gateway monitoring right now.

API Development with REST, GraphQL, WebSocket, and tRPC

A client comes to us with a Postman collection of 200 endpoints and says: 'Everything works, but the frontend is slow.' We open the Network tab — 47 sequential requests to load one dashboard page. Each one waits for the previous. This is not a server speed issue — it's an API architecture problem. With 10 years on the market, we've redesigned dozens of such integrations, and we guarantee: the right protocol and contract solve the problem at its root.

When REST stops being enough

REST works well for simple CRUD operations. But as soon as a mobile app appears alongside the web interface, over-fetching begins: the mobile app requests /api/users/123 and gets a 4KB object, but only needs name and avatar. Multiply that by a list of 50 users — 200KB traffic instead of 8KB.

GraphQL solves this with selection sets. The client describes exactly the fields it needs, and the server returns only those. On a project with React Native + Next.js, we migrated from REST to Apollo Server: payload size on the main screen dropped from 340KB to 28KB — a 92% traffic savings. Our certified engineers confirm: the typical pain when adopting GraphQL is N+1 query. A resolver for the author field on a post calls SELECT * FROM users WHERE id = ? for each post in the list. On a page with 20 posts — 21 database queries. Solved with DataLoader — it batches queries and turns them into one SELECT * FROM users WHERE id IN (...).

What is tRPC and how is it better than REST/GraphQL?

If the entire stack is TypeScript (Next.js + Node/Bun), tRPC removes a whole layer of problems. You define a procedure on the server — the client gets full type-safety automatically, without code generation and without Swagger. Renamed a field in the Zod schema — TypeScript highlights all places on the frontend where it's used. tRPC reduces code by 2 times compared to REST + Swagger + openapi-typescript: no need to maintain a separate specification and generate types — everything is inferred from runtime validators. However, tRPC is not suitable if the API is consumed by third-party clients or mobile apps in other languages — in such cases we use GraphQL or REST with OpenAPI specification.

WebSocket and real-time: when SSE, when WS?

HTTP polling every 5 seconds is an illusion of real-time with up to 5 seconds delay and useless server load. For chats, live notifications, collaborative editing — WebSocket or Server-Sent Events. SSE is a one-way stream from server to client, works over ordinary HTTP, automatically reconnects. Suitable for notifications, data streaming, progress bars. WebSocket is bidirectional, needed for chats and collaborative features. Experience shows: 80% of 'real-time' tasks are solved with SSE, not WebSocket — fewer infrastructure complexities.

A typical mistake: opening a WebSocket connection for each page component. On one project, the dashboard opened 12 parallel WS connections. The correct approach is one connection manager at the application level, subscriptions through it. In our work results, we always transfer the connection scheme and a ready solution.

Swagger / OpenAPI as a contract

Documentation written after the fact becomes outdated the day after release. We write the OpenAPI 3.1 specification before development starts; it becomes the contract between frontend and backend. The frontend generates types via openapi-typescript, the backend validates incoming data using generated schemas. Contract deviation from implementation is caught on CI, not during review. For Laravel — l5-swagger or dedoc/scramble. For Node.js — @fastify/swagger or Zod + zod-to-openapi.

How to properly authenticate an API?

JWT with long-lived access tokens without rotation is a source of problems when compromised. The correct scheme: access token for 15 minutes, refresh token for 30 days with rotation on each use. Refresh token stored in an httpOnly cookie, access token in memory (not in localStorage). For inter-service communication — API Keys with scope limitations or mTLS. OAuth 2.0 with PKCE for public clients (SPA, mobile).

How to handle versioning and backward compatibility?

Breaking changes in an API without versioning break clients. Three approaches we use in projects:

We guarantee backward compatibility through automated checks (oasdiff) on CI.

How we develop APIs: step-by-step plan

1. Analysis — audit of current integrations, data schema compilation, protocol selection (REST/GraphQL/tRPC/WebSocket).
2. Contract design — OpenAPI or SDL (GraphQL) before the first line of code.
3. Development — implementation per contract, unit tests for each endpoint.
4. Load testing — k6: 500 virtual users, 10 minutes, p95 latency ≤ 200ms.
5. Deployment — CI/CD with backward compatibility check, automatic documentation publication.
6. Team training — handover of Postman collection or Playground, connection instructions.

What is included (deliverables)

• OpenAPI 3.1 specification (or SDL for GraphQL).
• Generated client types for TypeScript / Dart / Kotlin.
• Set of automated tests covering all endpoints (unit + integration).
• Load tests (k6) and report (p50/p95/p99 latency, RPS).
• Documentation in Swagger UI / Redoc / GraphiQL.
• Team training (2–4 hour workshop).
• Support for 30 days after delivery (per contract).

Our experience

• 10+ years in the API development market.
• 200+ completed projects (REST, GraphQL, WebSocket, tRPC).
• 50+ certified engineers (AWS, Kubernetes, API Design).
• Traffic savings averaging 85% when migrating from REST to GraphQL for mobile apps.
• 100% backward compatibility — not a single broken client in the last 3 years.

Timeline

API development for a typical SaaS project with 30–50 endpoints: from 3 to 8 weeks depending on business logic complexity and number of external integrations. Migration of an existing REST API to GraphQL: from 2 to 6 weeks. Adding a WebSocket layer to an existing backend: from 1 to 3 weeks. Cost is calculated individually after an audit. Get a consultation — contact us to discuss your project.