From owner-freebsd-ports-bugs@freebsd.org Tue Dec 5 20:54:47 2017 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 26AFFE81442 for ; Tue, 5 Dec 2017 20:54:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 149A16F20B for ; Tue, 5 Dec 2017 20:54:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vB5Ksj6o049779 for ; Tue, 5 Dec 2017 20:54:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 223720] net-mgmt/prometheus: Update to 2.0.0 Date: Tue, 05 Dec 2017 20:54:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dor.bsd@xm0.uk X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2017 20:54:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223720 --- Comment #6 from David O'Rourke --- 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.=