It doesn't read from files unfortunately, but https://openobserve.ai/ is very easy to set up locally (single binary) and send otel logs/metrics/traces to. Here's how I run it locally for my little shovel project - https://github.com/bbkane/shovel#run-the-webapp-locally-with-openobserve. - Source: Hacker News / 4 months ago

I guess you could take a look at this: https://openobserve.ai/ It's in Rust to add some HN catnip. - Source: Hacker News / 9 months ago

Check https://openobserve.ai . It already has logs, metrics and traces and there is more on the horizon. - Source: Hacker News / 10 months ago

Probably migrating to https://openobserve.ai/ might help reduce dependencies. Source: 11 months ago

I also read that Salt was using MessagePack to format their messages. MessagePack is a format like JSON, but more compact. - Source: dev.to / 8 months ago

So appreciate such a detailed reply, thanks. btw, why did you choose tinylib/msgp from 4 available go-impls? Source: about 1 year ago

If you find you're running the serial connection at maximum speed and it's still not fast enough, try switching to a more compact binary encoding that has both Serde and Arduino implementations, like MsgPack... Though I don't remember enough about its format off the top of my head to tell you the easiest way to put an unambiguous header on each packet/message to make the protocol self-synchronizing. Source: over 1 year ago

The information can be stored in a database or as files, serialized in a standard format and with a schema agreed with your Data Engineering team. Depending on your information and requirements, it can be as simple as CSV, XML or JSON, or Big Data formats such as Parquet, Avro, ORC, Arrow, or message serialization formats like Protocol Buffers, FlatBuffers, MessagePack, Thrift, or Cap'n Proto. - Source: dev.to / over 1 year ago

MessagePack Similar to JSONs, just more compact, although not as much as the ones above. Still, it's usefull to retain some readability in your messages. Source: over 1 year ago