API observability that shows why a request failed
Logs in one tool, metrics in another and nothing that links an error to the change behind it. G8 shows request records, analytics and alerts in the gateway console, read from your own Prometheus and Elasticsearch or OpenSearch.
Answers spread across too many tools
When an API starts failing, the first questions are simple: which requests, since when and what changed.
Request details out of reach
Gateway logs are shipped somewhere else, and finding one request takes a query language.
With G8Traffic Explorer searches request records by path, client IP, request ID, Route or Consumer.
Errors without their cause
Charts show errors rising but not the change that came just before.
With G8Analytics shows the changes made in the same window, from the audit log, beside the charts.
Alerts nobody set up
Alerts on a gateway take a separate system and rules written by hand.
With G8G8 evaluates alert rules itself and sends alerts to mail lists and signed webhooks.
Request records, analytics and alerts in the gateway console
Each Environment reads its request counts from your Prometheus and its request records from your Elasticsearch or OpenSearch. Records and counts stay in the stores you run.
Request records with sensitive values masked
Traffic Explorer keeps the gateway’s own request records. Choose which headers, query arguments and body fields are masked before a record is stored, and how long records are kept.
- Bodies behind their own permissionViewing a request body takes its own permission and is written to the audit log.
- Copy as cURLCopy a request as cURL, or export the list as CSV.
Errors and response times beside the changes
Request counts beside last week’s with a projection to midnight, response time percentiles as the client, the backend and the gateway see them, and the Routes with the most errors. The changes made in the same window sit beside the charts.
- Gateway nodesSee which nodes receive traffic and which can’t be reached, with the reason.
Alerts that G8 evaluates itself
Rules on response share, response time or request count, for an Environment, a Route, a Service, an Upstream or a Consumer. System alerts tell you when the engine or Prometheus can’t be reached.
- Email and signed webhooksAlerts go to mail lists through your mail relay and to webhooks signed with HMAC-SHA256.
An API that started failing
A typical setup, drawn to show how the parts fit together. It doesn’t describe a specific customer.
An operations team runs the gateway for a set of payment APIs. One afternoon, errors on one Route start to rise.
A rule on the Route’s response share fires and reaches the team’s mail list and webhook.
Analytics shows the errors rising and, in the same window, a change to the Route’s Upstream with the person who made it.
In Traffic Explorer the team filters by Route and status and opens a failing record.