3 ms·
I invite your attention to the StatsD telemetry protocol, where: 1. Every single measurement in a timeseries is encoded as a utf-8 string having (roughly) the
by jcgrillo 1y ago
I invite your attention to the StatsD telemetry protocol, where:
1. Every single measurement in a timeseries is encoded as a utf-8 string having (roughly) the following format:
"${name}:${value}|${type}|${tags}"
where name is like "my.long.namespace.and.metric.name", value is a string formatted number, god only knows what type is, and tags is some gigantic comma separated key:value monstrosity.
2. Each and every one of these things is fired off into the ether in the form of a UDP datagram.
3. Whenever the server receives these presumably it gets around sometime to assigning them timestamps and inserts them into a database, not necessarily in that or any other particular order.
"it is the way it is[1]."
[1] https://github.com/statsd/statsd?tab=readme-ov-file#usage https://github.com/statsd/statsd?tab=readme-ov-file#usage
- godelski 1y agoI think NodeJS goes against the idea of writing good and efficient software... JS just creates unnecessary complexity
- jcgrillo 1y agoI don't really know anything about js but this metrics protocol is how most telemetry data is transmitted on the wire. Petabytes per day of bandwidth are wasted on this.