On 25 Nov 10:35, Fabian Reinartz wrote: > The point on TSDB becoming more structured is interesting – how firm are > these plans at this point? Any rough timelines? > My first hunch would've been to explore integrating directly at the > scraping layer to directly stream OpenMetrics (or a proto-equivalent) from > there, backed by a separate, per-write-target WAL. > This wouldn't constrain it by the currently supported storage data model > and generally decouple the two aspects, which also seems more aligned with > recent developments like the agent mode. > Any thoughts on that general direction?
As maintainer of Prometheus server, in general, I am worried that getting a wal that'd be more "able" than the actual Prometheus TSDB would weaken the Prometheus server use case in favor of SaaS platforms. It does not sound great for the users who rely on Prometheus alone, which I think will continue to represent a large part of our community in the future. Additionally, the Query Engine should take advantage of those new properties as well: until we do not support that in Prometheus TSDB, it's harder to take advantage of the OpenMetrics types in the language. -- Julien Pivotto @roidelapluie -- You received this message because you are subscribed to the Google Groups "Prometheus Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-developers/20211125212505.GA1108440%40hydrogen.
