Got it, thanks a lot for your detailed answer! 

In our use case, we don't need to change existing values. I think I would 
love to still try Prometheus on our data and queries. 

Back to my initial question about loading data to Prometheus from a CSV 
file. I realize this cannot be done and the data has to be converted. I am 
just wonder what format it should be converted to and if I can get a sample 
of the required format. Also, are there any resources/tutorials about 
loading historical data to Prometheus? 

Thanks a lot! 

Best,
Abdel 

On Monday, March 27, 2023 at 3:20:47 PM UTC+2 Stuart Clark wrote:

> On 2023-03-27 13:22, Abdelouahab Khelifati wrote:
> > Hello Stuart, thanks for reaching out!
> > 
> > I see your point!
> > 
> > My data does contain only numerical data, has a constant rate, and
> > only has one string label. Would you say that it is possible but not
> > optimal or simply not possible to use Prometheus as a general-purpose
> > database?
> > 
> > Also, would it be possible to point out the main technical factors
> > rendering Prometheus unsuitable as a general-purpose database?
> > 
>
> Well the TDSB in Promethues could be used elsewhere if you created code 
> (as I think the TDSB code is fairly abstracted from other parts of 
> Prometheus) but otherwise all interactions are via the rest of 
> Prometheus. So for example the main way of populating the database is 
> via scraping targets. There is no way to change existing data (other 
> than deleting things). There is only a single schema (each timeseries 
> contains a single float64 per data point with a list of string based 
> labels [the metric name is actually a label]).
>
> So I'd suggest that the TDSB is as it stands very much not a 
> general-purpose database - it is just a integral part of Promtheus, 
> designed for the use case of regular live numeric metric values, with 
> the ability to extract values via PromQL for graphing/alerts/etc. If 
> your use case aligns with that, then it could be a good fit, but if you 
> are wanting other things (being able to change values, doing a lot of 
> bulk importing, wanting to run/scale the database separately, wanting 
> database reliability/HA similar to other general purpose databases) it 
> may be a poor fit.
>
> -- 
> Stuart Clark
>

-- 
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/7c474d2d-16b9-465b-a336-db7fb1d1e50dn%40googlegroups.com.

Reply via email to