Skip to main content

Logging & Monitoring

Boltic Gateway offers powerful observability features to help you track, debug, and optimize API traffic at both the request level and gateway level. With real-time metrics and structured logs, developers and SREs can quickly identify issues, analyze performance trends, and ensure smooth operation of services.

Request & Execution Logs​

  • Log Availability: Logs are retained and made accessible with a typical delay of up to 5 minutes, ensuring near real-time visibility without impacting performance.

    Logs

  • Log Granularity: Every request processed by the gateway generates a structured execution log that includes:

    • Request ID (CF-Ray)

    • Route matched

    • Downstream URL

    • Response status

    • Middleware activity

    • Latency (gateway processing time)

      Individual Log

  • Log Filtering Options: Logs can be filtered in the dashboard or API using:

    • Request ID – Useful for tracing individual requests across systems.
    • Severity – Filter logs by severity levels (INFO, WARN, ERROR).
    • Environment – View logs scoped to either Test or Production.

  • Use Cases:

    • Trace failing requests in production.
    • Monitor deployment impact on route behavior.
    • Audit sensitive API interactions.
    • Debug header rewrites and middleware output.

Real-Time Monitoring​

Boltic Gateway surfaces actionable metrics to help you understand usage patterns, troubleshoot performance issues, and monitor health at both the route level and gateway level.

Gateway-Level Metrics​

Provides an overview of the overall health and traffic of your entire gateway instance.

  • Total Requests – Count of incoming requests over time.

  • Error Rate – Percentage of 4xx/5xx responses across all routes.

  • Average Gateway Latency – Time spent within Boltic Gateway (excluding downstream latency).

  • Top Routes by Volume – High-traffic endpoints in your gateway.

    Gateway-Level Metrics

Route-Level Metrics​

Enables deep dive into performance and reliability of specific routes.

  • Requests per Route – Number of hits to a specific path or integration.

  • Response Codes Breakdown – View how many requests returned 2xx, 4xx, 5xx responses per route.

  • Latency per Route – Time spent processing and routing specific requests.

    Route-Level Metrics List
    Single Route Metric

Best Practices​

  • Use Request ID tracing across your observability stack for end-to-end debugging.
  • Monitor gateway latency separately from backend latency to isolate bottlenecks.
  • Regularly audit error rates at the route level to identify failing endpoints.
  • Leverage top route metrics to optimize high-traffic paths with caching, batching, or rewrites.

With its comprehensive logging and monitoring capabilities, Boltic Gateway empowers developers and ops teams to maintain high reliability, diagnose issues fast, and continuously optimize performance across environments.