Re: NEW: prometheus-2.0.0

On 2018/01/01 16:04, Claudio Jeker wrote:
> On Sun, Dec 31, 2017 at 01:00:44PM +0000, Stuart Henderson wrote:
> > On 2017/12/31 09:40, Antoine Jacoutot wrote:
> > > On Sun, Dec 31, 2017 at 08:12:07AM +0000, Claudio Jeker wrote:
> > > > Hi,
> > > >
> > > > Here is a port of prometheus 2.0.0.
> > > >
> > > > Prometheus is an open-source systems monitoring and alerting toolkit.
> > > > Its main features are:
> > > > - a multi-dimensional data model with time series data identified by
> > > > metric name and key/value pairs
> > > > - a flexible query language to leverage this dimensionality
> > > > - no reliance on distributed storage; single server nodes are autonomous
> > > > - time series collection happens via a pull model over HTTP
> > > > - pushing time series is supported via an intermediary gateway
> > > > - targets are discovered via service discovery or static configuration
> > > > - multiple modes of graphing and dashboarding support
> > >
> > > Awesome :-)
> > > Nitpicking:
> > > - in the rc.d script, $daemon_flags -> ${daemon_flags} (for consistency)
> > > - in the rc.d script, ${_bg} is not needed
> > >
> > > Rest looks fine, OK aja
> > >
> > >
> > > --
> > > Antoine
> > >
> >
> > Wondering about the log redirect. Could it pipe through logger(1) instead?
>
> Could be an option. I could change it to:
> logger -p daemon.info -t prometheus
>
> If that is preferred I'm happy to do that, I prefer syslog over random
> log files.

If it works with that, yes please, apart from anything else random
log files are hard to rotate and prone to filling the loggin disk..

I've just tried building it, but there's a problem, it tries to do
a github checkout during the build:

===> Building for prometheus-2.0.0
cd /usr/obj/ports/prometheus-2.0.0/go/src/github.com/prometheus/prometheus && GOPATH=/usr/obj/ports/prometheus-2.0.0/go gmake build
>> fetching promu
# cd .; git clone https://github.com/prometheus/promu /usr/obj/ports/prometheus-2.0.0/go/src/github.com/prometheus/promu
Cloning into '/usr/obj/ports/prometheus-2.0.0/go/src/github.com/prometheus/promu'...
fatal: unable to access 'https://github.com/prometheus/promu/': Couldn't connect to server
package github.com/prometheus/promu: exit status 128

On my system, same as at least some of the bulk build machines, the
port build user doesn't have net access - all the fetching needs to be
done by ports infrastructure[1].

I'm not sure how best to handle this, I think some other ports resorted
to building their own custom tarballs with the dependencies included,
though in this case another option might be a separate port for promu
and patch the build infrastructure to use it.

Maybe someone who works on go ports might have a better idea..



[1] (Thanks to espie's recent work this is easy to setup:
PORTS_PRIVSEP=Yes, the ports work directory needs to be writable by
_pbuild, /usr/ports/distfiles needs to be writable by _pfetch, and
"block quick proto {tcp udp} user _pbuild" in PF).