search

graphite-project / graphite-web

A highly scalable real-time graphing system
http://graphite.readthedocs.org/
Apache License 2.0
5.89k stars 1.26k forks source link

[Q] What's the best way to auto-update this project on a server? #2725

Closed jguzman-tech closed 2 years ago

jguzman-tech commented 2 years ago

We're trying out graphite as a data source instead of prometheus on an HPC server, because graphite's downsampling feature is important for reducing disk usage over long timeframes. Our main concern is how to auto-update in case there are security updates. We aren't using docker but it seems like the source install is preferred since it's used in the dockerfile here. And it seems unsafe to automatically do a fresh source install each time.

Any advice on how to keep our instance of graphite up-to-date?

jguzman-tech commented 2 years ago

Any tips here? Or is the best way of updating graphite to re-install, and copy over the old config files and the whisper data directory?

deniszh commented 2 years ago

Hi @jguzman-tech

Graphite is multi-component complex system, written in Python, hence has quite big dependency tree. Also, it contains database, and auto-updates for databases is generally bad idea. I'm afraid it's not really possible to implement reliable auto update for Graphite or similar system, if it's not designed especially for it from scratch - which is not the case. OTOH - usually we're not introducing breaking changes, so, you can update python packages and use then with old config files and data - that could be good enough, but not gurantee anything ofc.

jguzman-tech commented 2 years ago

@deniszh Thanks, I appreciate the response. This is very reasonable, but felt that I had to double check.