Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Prometheus 2.0

prometheus.io

Post reply on HN
Print view View original

11–20 of 43 posts

Re: Prometheus 2.0

#11

Post by bbrazil »

sz4kerto wrote: post #7

No good migration story for existing data, that'll hurt us quite a lot. :(

There is a transition feature: https://www.robustperception.io/accessing-data-from-promethe...

The problem with data migration is that the two versions of the system lay out the data quite differently, so converting from one to the other would take a lot of disk seeks. In the worst case you could be looking potentially at days to convert the data over, which isn't really an option for most systems that care about older data.

Re: Prometheus 2.0

#12

Post by sz4kerto »

jrv wrote: post #8
sz4kerto wrote: post #7

No good migration story for existing data, that'll hurt us quite a lot. :(

Yeah, as Prometheus's local storage is meant more as a transient / non-durable metrics store, the only current way to migrate while simultaneously accessing old and new data is to run both the old and new servers and have the new one read old data from the other one via the remote-read integration. Someone could write a tool to do a full migration of the old storage format to the new one, but the formats are complete…

> EDIT: If you would like to fund development of such a tool, let us know :)

We're too small for that, unfortunately. Someone said at DockerCon that migrating large (multi-TB) stores would take a long time; this doesn't apply to us, we have only ~0.1 TB perf data as of now.

Re: Prometheus 2.0

#14

Post by SEJeff »

frik wrote: post #5

Does Prometheus 2 still use the unmaintained charting library "flot charts" ? http://www.flotcharts.org/ No commits since 2014. Unfortunately, because it's a great chart library (actually probably the best free one), only the reliance on JQuery isn't that fashionable. Edit: oh, it was Grafana and Kibana that used Flot charts (at least when I tried it two years ago, maybe things have changed) quick Google (2014): http…

This is one of the other "better" charting libraries, and it is maintained: http://nvd3.org/

Re: Prometheus 2.0

#15

Post by SEJeff »

SkyRocknRoll wrote: post #2

Does this storage engine onpar with influxdb ?

FWIW, when I met Paul Dix a few months ago, he had nothing but good to say about the new Prometheus. They released this blog post shortly after our meeting:

https://www.influxdata.com/blog/influxdb-now-supports-promet...

I wouldn't see them as competitors so much as complimentary. Influx is really going for the long term tsdb storage, whereas prometheus is more shorter term with higher resolutions and alerting.

Re: Prometheus 2.0

#17

Post by bbrazil »

the_arun wrote: post #16

How Prometheus compares to Splunk?

Splunk is a event logging system, compared to Prometheus which is metrics based. You need both types of systems to be able to properly observe your systems, they're complementary.

Re: Prometheus 2.0

#18

Post by jrv »

sz4kerto wrote: post #12
jrv wrote: post #8

Earlier quoted context omitted.

Yeah, as Prometheus's local storage is meant more as a transient / non-durable metrics store, the only current way to migrate while simultaneously accessing old and new data is to run both the old and new servers and have the new one read old data from the other one via the remote-read integration. Someone could write a tool to do a full migration of the old storage format to the new one, but the formats are complete…

> EDIT: If you would like to fund development of such a tool, let us know :) We're too small for that, unfortunately. Someone said at DockerCon that migrating large (multi-TB) stores would take a long time; this doesn't apply to us, we have only ~0.1 TB perf data as of now.

Out of curiosity, do you care about migrating the data online, or would a brief Prometheus downtime (and thus gap in data) be ok?

Re: Prometheus 2.0

#19

Post by sz4kerto »

jrv wrote: post #18
sz4kerto wrote: post #12

Earlier quoted context omitted.

> EDIT: If you would like to fund development of such a tool, let us know :) We're too small for that, unfortunately. Someone said at DockerCon that migrating large (multi-TB) stores would take a long time; this doesn't apply to us, we have only ~0.1 TB perf data as of now.

Out of curiosity, do you care about migrating the data online, or would a brief Prometheus downtime (and thus gap in data) be ok?

Downtime would be acceptable I think, especially because we could just launch a separate instance of Prom while the main one is being migrated.

Re: Prometheus 2.0

#20

Post by sz4kerto »

bbrazil wrote: post #11
sz4kerto wrote: post #7

No good migration story for existing data, that'll hurt us quite a lot. :(

There is a transition feature: https://www.robustperception.io/accessing-data-from-promethe... The problem with data migration is that the two versions of the system lay out the data quite differently, so converting from one to the other would take a lot of disk seeks. In the worst case you could be looking potentially at days to convert the data over, which isn't really an option for most systems that care about old…

Seek time is not relevant, our stuff is on SSDs. Thanks for the link, I've known about the transition feature.
Post reply on HN