Date: Tue, 05 Dec 2017 20:54:46 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 223720] net-mgmt/prometheus: Update to 2.0.0 Message-ID: <bug-223720-13-UPPyaGGikL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-223720-13@https.bugs.freebsd.org/bugzilla/> References: <bug-223720-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223720 --- Comment #6 from David O'Rourke <dor.bsd@xm0.uk> --- After considering this for a while, and speaking with some other FreeBSD porters, the best thing is probably to continue with the `prometheus2` pack= age. However, it should not conflict with the `prometheus` package, as both are required to run together for the migration period if a user wishes to take = that path. This means the binaries become `prometheus2` and `promtool2`, the config becomes `prometheus2.yml`, the pidfile becomes `prometheus2.pid`, the rc.co= nf variables receive similar treatment, etc. In this case, a few words in the `pkg-message` linking to the migration gui= de on the Prometheus site, should suffice. People can then work out what they = need to do to fix up their old config to work with Prometheus 2 while not losing access to their old data immediately. The most complicated part is likely t= o be alerting and recording rules, but `promtool` can help with that and instructions for this are in the migration guide too. Viewing the `prometheus2.shar` that was submitted (which looks good), this should just be a few minor changes. -David --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-223720-13-UPPyaGGikL>