[Bug 223720] net-mgmt/prometheus: Update to 2.0.0

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Dec 5 20:54:47 UTC 2017


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223720

--- Comment #6 from David O'Rourke <dor.bsd at 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` package.

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.conf
variables receive similar treatment, etc.

In this case, a few words in the `pkg-message` linking to the migration guide
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 to 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

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list