Exploring observability options for quantum SDK workflows runs (Qiskit, Cirq, etc.)
Summarize this article with:
Hi all, A few weeks ago we shared an early version of QObserva here and got some useful feedback, so we wanted to share a small follow-up as we continue iterating on it. The idea behind QObserva is fairly simple: adding lightweight observability around quantum SDK workflows — things like run metadata, tags, backend context, and experiment tracking across Qiskit/Cirq-style workflows. One thing that’s been interesting so far is seeing how different people structure and track runs today. Some rely mostly on notebooks, some use internal tooling/scripts, and others keep things intentionally lightweight. We’re still very early and mostly trying to understand: what information people actually care about during runs what becomes difficult to track over time what kind of visibility is genuinely useful vs unnecessary noise Repo: https://github.com/BuildersArk/qobserva It’s still evolving, but we’d genuinely appreciate feedback from people experimenting in this space. submitted by /u/qobserva_labs [link] [comments]