Hello! We’re currently using Netdata’s Prometheus remote write exporter to send metrics over to GreptimeDB. The data volume increases pretty quickly, leading us to have thousands of tables. In InfluxDB, we can manage downsampling with continuous queries at the database level. However, in GreptimeDB, it seems like flows only work for a single table. Creating and maintaining flows for so many tables is extremely challenging, especially as new tables keep getting created. Is there a way to set up a database-scoped flow (like

FROM source_database.*

) that would automatically downsample all tables in a database? If not, is this feature planned or on the roadmap?

hi @silverfox23, yes we have downsample feature in our backlog. We may not implement it as a flow task because it's going to be expansive for historical data. Also note that for prometheus data, we have a concept called logical table. These thousands of tables are actually 1 physical greptimedb table. So it will not overwhelming your metadata.

Ah, I see! That feature would be great. When do you plan to implement it? Right, I saw the metric table engine concept. I was wondering if one could define a flow on the physical table to implement a downsampling of all (logical) tables but that doesn't seem to be the case.

We don't have an ETA for now..