Gateway Traffic Review

A Gateway Traffic Review is a time-bounded reading of what your gateway actually served. It is for teams who already run routes through a reverse proxy, an API gateway, or a similar front door, and who need those hours turned into charts a person can hold.

The result is a bound briefing: time-series of request volume, latency at the median and at the tail, status-code weather by route, and a short list of upstreams that took unusual weight. Captions sit in the margin. We do not ship a live board you must keep open.

What is in the sitting

You name the window — often seven to fourteen days, sometimes a single bad morning. We agree the routes that matter and the fields you can actually export: timestamp, route, status, upstream, duration. Traces help when you have them; they are not required.

The desk then draws. Error clusters get a start minute and an end minute. Timeouts are kept apart from application 500s. If a certificate renewal or a deploy ticket sits inside the window, we plot it as a vertical rule so the room can argue with a clock instead of a feeling.

The sitting itself is two hours. In Batumi we lay the sheets on the table at Level 7. By video we share the same pages and stop on each caption. You keep the briefing. We keep a copy for thirty days unless you ask us to destroy it sooner.

What is left out

We do not take the keys to the gateway. We do not rewrite location blocks, rate-limit rules, or WAF policies as part of this sitting. We will write questions those configs might answer; changing them is your change window, not ours. On-call cover is not included. A standing monthly reading is a different sitting.

Who sits with you

Giorgi Tskitishvili reads the logs. Nino Beridze prepares the charts. Ana Khurtsidze sets type and caption so the briefing can be read without us in the room. If only one of us can attend the sitting, we say so when we confirm the date.

Timing and place

Ten working days is the ordinary span from a usable sample to the sitting. A sample is “usable” when clocks agree, routes are named, and the file is not a screenshot of a terminal. Work happens at the Batumi desk; the sitting may be there or on a video call. We do not travel on this sitting unless a separate day rate is agreed.

Constraints

We read what you can legally send. Production payloads with card numbers or medical notes must be stripped before they leave your house. If the log is sampled at one-in-twenty, we will say so on every chart that inherits the sample. Windows longer than thirty days are split, not flattened into a single average line.

Price and the next step

The fee is quoted from the sample: number of routes, length of the window, whether traces exist, and whether you need a same-week sitting. The published starting figure is on the rates page. A third of the fee is due when we accept the files; the rest after the sitting. Write to the desk with dates and format — that letter is the start, not a software trial.