4 ms·
OT but still sooo weird to me the text exposition format is the only format. for embedded devices (like this lib targets), having the now-removed protobuf expo
by rektide 4y ago
OT but still sooo weird to me the text exposition format is the only format.
for embedded devices (like this lib targets), having the now-removed protobuf exposition format seems like such an easy win. less memory & less work & less bandwidth.
- bboreham 4y agoIt was added back to Prometheus. https://github.com/prometheus/docs/blob/main/content/docs/instrumenting/exposition_formats.md https://github.com/prometheus/docs/blob/main/content/docs/in...
- EdSchouten 4y agoI think the reason for that is that Protobuf doesn’t provide streaming parsers (yet). As the Protobuf based protocol stored all samples in a single message, this meant that both the client and server had to allocate lots of memory when sending/receiving metrics. With the text based protocol this was never an issue, as the process that does the scraping can ingest metrics line by line.
- mgaunard 4y agoWhy do you care? Even if you have thousands of metrics, this is still relatively little data. This also presumably runs on an auxiliary thread, and uses a network interface not tied to production services.