Kong Gateway Integration
API gateway request metrics, plugin latency, and upstream health monitoring for Kong Gateway. Track every route, service, and consumer with AI-powered anomaly detection and root cause analysis.
How It Works
Enable Prometheus Plugin
Add the Kong Prometheus plugin globally or per-service. The plugin exposes /metrics on the Kong admin port with route, service, upstream, and plugin latency metrics in Prometheus format.
Configure TigerOps Scraping
Add the Kong metrics endpoint to TigerOps scrape configuration. TigerOps scrapes Kong Prometheus metrics every 15 seconds and indexes route, service, and consumer labels.
Enable HTTP Log Plugin
Add the Kong HTTP Log plugin to stream access logs to TigerOps. Configure the plugin to include plugin latency breakdown, upstream latency, and consumer identity fields.
Configure Upstream Health Alerts
Set alerts for Kong upstream health check failures and passive health check trip thresholds. TigerOps correlates upstream unhealthy events with route error rate increases automatically.
What You Get Out of the Box
Route and Service Metrics
Per-route and per-service request counts, latency histograms (p50/p95/p99), bandwidth, and HTTP status code distribution. TigerOps tracks SLOs per route across your entire API surface.
Plugin Latency Attribution
Kong Prometheus plugin exposes per-plugin latency overhead. TigerOps identifies which plugins (rate-limiting, JWT auth, request-transformation) add the most latency to your API requests.
Upstream Health Check Monitoring
Track Kong active and passive health check results per upstream target. TigerOps alerts on upstream target failures, circuit breaker trips, and automatic recovery events in real time.
Consumer-Level Rate Limit Tracking
Monitor rate limit consumption per Kong consumer and credential. TigerOps tracks remaining quota, rate limit violations, and identifies consumers approaching their limits before they hit 429 errors.
Kong Cluster Node Monitoring
Track Kong cluster node health, database connection pool metrics (PostgreSQL or Cassandra), and Kong worker memory usage. AI detects database connection exhaustion before it impacts API availability.
AI Root Cause on Gateway Errors
When Kong error rates spike, TigerOps AI analyzes correlated signals — upstream timeouts, plugin errors, database latency, and consumer traffic patterns — and identifies the root cause automatically.
Kong Prometheus and HTTP Log Plugins
Enable Kong plugins for metrics and log forwarding to TigerOps using decK or the Admin API.
# decK configuration for Kong plugins
# Apply with: deck sync -s kong-tigerops.yaml
_format_version: "3.0"
plugins:
# Global Prometheus metrics (all routes and services)
- name: prometheus
enabled: true
config:
per_consumer: true
status_code_metrics: true
latency_metrics: true
upstream_health_metrics: true
bandwidth_metrics: true
# Global HTTP log forwarding to TigerOps
- name: http-log
enabled: true
config:
http_endpoint: https://ingest.atatus.net/kong/logs
method: POST
content_type: application/json
timeout: 10000
keepalive: 60000
flush_timeout: 2
retry_count: 10
headers:
Authorization: "Bearer ${TIGEROPS_API_KEY}"
custom_fields_by_lua:
plugin_latency: "return (kong.ctx.shared.proxy_latency or 0)"
# TigerOps scrape target for Prometheus metrics:
# scrape_configs:
# - job_name: kong
# static_configs:
# - targets: [kong-admin:8001]
# metrics_path: /metricsCommon Questions
Which Kong version and deployment modes does TigerOps support?
TigerOps supports Kong Gateway 2.x and 3.x (OSS and Enterprise), Kong Ingress Controller, and Kong Konnect. The Prometheus plugin works identically across all deployment modes.
How do I get per-route metrics from Kong?
Enable the Prometheus plugin with per_consumer and status_code_metrics options enabled. Add the route label to your scrape configuration. TigerOps automatically groups metrics by kong_route, kong_service, and kong_workspace labels.
Can TigerOps monitor Kong Ingress Controller on Kubernetes?
Yes. The Kong Ingress Controller exposes Prometheus metrics at /metrics on port 10255. Use TigerOps pod annotation-based auto-discovery (prometheus.io/scrape=true) to automatically scrape KIC metrics from all pods.
How does TigerOps handle Kong Enterprise workspace metrics?
Kong Enterprise exposes metrics tagged with the kong_workspace label. TigerOps stores and queries workspace-level metrics, allowing you to compare API performance across workspaces and isolate tenant-specific issues.
Can I track Kong plugin configuration changes in TigerOps?
Yes. Use the Kong Admin API webhook or Deck sync events to send configuration change notifications to TigerOps. TigerOps marks plugin configuration deployments on metric timelines for correlation with performance changes.
Full API Gateway Observability for Kong
Per-route SLO tracking, plugin latency attribution, upstream health monitoring, and AI root cause analysis. Enable in 5 minutes.