Created
May 21, 2026 15:10
-
-
Save melvinlee/ce5ff32879ef6b1c82faa824e709c3c9 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 1. Traffic Overview | |
| ▎ "Look at Kong logs for the last 24 hours. Count requests by status code (2xx, 3xx, 4xx, 5xx) per hour. Which paths are generating the most errors? Show me sample failing requests so I | |
| ▎ can see what's broken." | |
| --- | |
| 2. Slow Requests | |
| ▎ "Find all Kong requests that took longer than 1 second in the last hour. Which endpoints are slowest? Is the slowness on one specific route or spread across everything — and is it | |
| ▎ getting worse over time?" | |
| --- | |
| 3. Auth Failures & Abuse | |
| ▎ "Show me all 401 and 403 responses from Kong in the last 6 hours. Which client IPs are hitting auth errors the most? Flag anything over 50 failures — that's either a broken API key or | |
| ▎ someone probing the gateway." | |
| --- | |
| 4. Rate Limiting Patterns | |
| ▎ "Find all 429 responses from Kong in the last 24 hours. Is one IP hammering many different endpoints (bot), or are many IPs hitting the same endpoint (popular route that needs a higher | |
| ▎ quota)? Plot the 429s over time so I can see if there are burst spikes." | |
| --- | |
| 5. Upstream Failures | |
| ▎ "Kong is returning 502, 503, or 504 errors. Look at the last 2 hours and tell me: when did it start, which routes are affected, and is it still happening or has it recovered? I need to | |
| ▎ know if this is one upstream service down or the whole gateway." |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment