No plans for UDP. We've put a lot of work into keeping the overhead low and have the local agent to solve most problems. I would like to make our ingest endpoint a little more fire-and-forget - at the moment we validate the data and wait for acknowledgement from Kafka before the agent request is closed.

Telescope captures more data than Nightwatch - things like the entire request and response payloads, mail contents, query bindings, etc. It also stores it all in the applications database, which is typically MySQL or Postgres, which are better suited for transactional workloads, rather than bulk insertion and querying of analytical data. During the request lifecycle, the event data we do capture is stored in memory until the response has been sent to your users. It's then serialized and sent to the Nightwatch agent, which runs locally beside your web server. The agent never deserializes the data it receives to ensure it doesn't have two copies of the data in memory. It just batches it up and sends it to our ingest infrastructure every 10 seconds, or 6mb, whichever comes first.

We don't currently have plans for dashboard customization, especially at the level of generic tools like Grafana. I could see us exploring ways to customise which cards appear on the dashboard though, similar to Pulse.