At first I assumed this was similar to trace IDs, but it’s solving a different problem.

This is more like giving stable IDs to individual log statements (e.g. “upload started”, “upload retrying”, “upload failed”, “upload completed”), so you can see higher-level trends.

It makes it easy to see whether failures dropped after releasing a fix, without relying on fragile text searches.

Useful for team leads or engineering managers who want a high-level view of how system behavior changes over time.

Exactly. The combination of trace IDs and statement IDs is also a very interesting topic as it has the potential to provide an abstracted view of the runtime behaviours of a system, making is easier to spot when those changes (e.g. as a result of a new version release).

I’ve been experimenting with data formats like Parquet and Iceberg, and recently came across Lance. I wanted to try building something around it.

So I put together a simple Digital Asset Manager (DAM) where:

* Images are uploaded and vectorized using CLIP

* Vectors are stored in Lance format directly on Cloudflare R2

* Search is done via Lance, comparing natural language queries to image vectors

* The whole thing runs on Fly.io across three small FastAPI apps (upload, search, frontend)

No Postgres or Mongo. No AI, Just object storage and files.

You can try it here:

* https://metabare.com/

Or see the code here:

* https://github.com/gordonmurray/metabare.com

Would love feedback or ideas on where to take it next — I’m planning to add image tracking and store that usage data in Parquet or Iceberg on R2 as well.

Working in it

I've added a Description now

Hi Pmtarantino, Yup, that's the next thing I'll add, just getting it out there at the moment to see if there is any interest in it.