| ▲ | oulipo2 9 hours ago | |
Seems cool! But would be nice to have some "real-world" use cases to see actual usage patterns... In my case my systems can produce "warnings" when there are some small system warning/errors, that I want to aggregate and review (drill-down) from time to time I was hesitating between using something like OpenTelemetry to send logs/metrics for those, or just to add a "warnings" table to my Timescaledb and use some aggregates to drill them down and possibly display some chunks to review... but another possibility, to avoid using Timescaledb/clickhouse and just rely on S3 would be to upload those in a parquet file on a bucket through duckdb, and then query them from time to time to have stats Would you have a recommendation? | ||
| ▲ | citguru 2 hours ago | parent | next [-] | |
The project is still fairly new and not close to production tbh. I'd actually recommend the simplest option: just write them to Parquet on S3 and query with plain DuckDB. Or you could use Ducklake - https://ducklake.select/ | ||
| ▲ | throwatdem12311 6 hours ago | parent | prev [-] | |
There is no “real world” use case because it’s vibe coded slop. | ||