Closed danie1k closed 4 months ago
There is a great alternative to InfluxDB, called VictoriaMetrics. I use it on production for a quite some time.
It exposes query/write API fully compatible with native InfluxDB, but scrutiny requires a specific endpoint that VictoriaMetrics does not implement:
https://github.com/AnalogJ/scrutiny/blob/a3dfce3561bcddcd8b70e4e7f483e22594c8af4d/webapp/backend/pkg/database/scrutiny_repository.go#L236-L239
Could you change the implementation, so this endpoint won't be needed, or could this boot step could be skipped conditionally?
I wasn't quite right. VictoriaMetrics has fully InfluxDB-compatible write endpoints, but doesn't provide InfluxDB query (read) endpoints - only Prometheus one.
There is a great alternative to InfluxDB, called VictoriaMetrics. I use it on production for a quite some time.
It exposes query/write API fully compatible with native InfluxDB, but scrutiny requires a specific endpoint that VictoriaMetrics does not implement:
https://github.com/AnalogJ/scrutiny/blob/a3dfce3561bcddcd8b70e4e7f483e22594c8af4d/webapp/backend/pkg/database/scrutiny_repository.go#L236-L239
Could you change the implementation, so this endpoint won't be needed, or could this boot step could be skipped conditionally?