Menu

Post image 1
Post image 2
1 / 2
0

I redirected laravel/nightwatch to my own Postgres and hit 13,400 payloads/s on a single instance

DEV Community·Leonce Medewanou·27 days ago
#nXExXk05
#layer#laravel#php#postgres#agent#drain
Reading 0:00
15s threshold

If you run a Laravel app on a hosted observability platform like Nightwatch, you've probably sampled your telemetry down to keep the bill manageable. I wanted to keep all of it. laravel/nightwatch is Laravel's official observability SDK and the instrumentation itself is genuinely good. It's the hosted side that bothered me. Ingestion is usage-priced, throughput is bounded by what you're willing to pay for, and your telemetry lives in someone else's warehouse. Plenty of teams are happy with that trade. Others aren't: high-traffic apps that don't want to sample, regulated stacks where stack traces can't leave the perimeter, smaller teams whose Postgres already has the headroom to absorb the writes. They want the same SDK pointed somewhere else. So I wrote an agent that intercepts Nightwatch's ingest binding and redirects payloads to a local TCP socket, then drains them into a Postgres database I provision. On a single instance it sustains around 13,400 payloads/s .…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More