Kong
A plugin at the gateway covers every service behind it at once.
“Payments API gateway” already reports from here. Another one gets its own write key and lands in the same table.Open
Take the write key
Everything this install sends is tagged with it, so one key per environment keeps staging out of your production numbers.
Generating…Install
One package, in the service you are instrumenting.
luarocks install kong-plugin-clearplaneAdd it to Kong
Paste this where the request path is assembled. The account callback is the only part you have to fill in — it is what turns a request into a customer.
yaml
plugins:
- name: clearplane
config:
write_key: ${CLEARPLANE_KEY}
account_header: X-Org-IdName this install
Name it for the deployment rather than the framework. Two Next.js apps in one workspace is the normal case, and “Next.js” twice helps nobody.
Environment
Events land in events_kong and are queryable from Chat, models, and SQL.