Harkishen Singh
Harkishen Singh
Signed-off-by: Harkishen-Singh Note: the folder `pkg/tests/testdata/bench_data.zip` is of `20.9 MB`. Should we fetch this from s3 rather keeping in repo?
In https://github.com/timescale/promscale/pull/1286, we separated the migration-tool files under `migration-tool` which had its own mod file. However, this caused `gosec` to warn about imports, which looked like false positives to me....
At present, database metrics are evaluated with a context timeout to control database load. But, this may not be accurate since a context cancel may not stop the already executing...
We improved the telemetry collection in Promscale. We log about telemetry collection as warning and provide a link to TimescaleDB docs page. This should be done in a Promscale telemetry...
Version upgrades can have a good number of changes in SQL objects, specifically if one is using a old promscale version. Promscale should warn the changes or schema version changes...
Signed-off-by: Harkishen-Singh Reference: https://github.com/prometheus/prometheus/issues/9327
The current querier implementation is healthy enough for running a lot of queries in parallel as a set. This should be benchmarked as well so as to keep a track...
This is a draft PR. Complete details will be written once things are implemented. Silent features (mostly TODO): 1. Columnar based inserts 2. ability to handle unordered inserts 3. binary...
**Is your feature request related to a problem? Please describe.** JSON parsing and writing are costly. The cost increases when this happens at every commit, which is what our current...
PR #435 added support for null blocks. However, when opening the monitoring screen, the logs show errors as shown in the snapshot. This requires to be fixed (and not a...