dustin/metricspi/pipeline/pr-master There was a failure building this commitDetails
Switching from the `golang-package` macro to the `generic-package` macro
in order to make use of upstream's makefiles. This will ensure that the
correct flags are passed to the Go compiler, especially those related to
embedding the version string in the binary. Without this, the
`vm_app_version` metrics exposed by each application will be empty.
dustin/metricspi/pipeline/head This commit looks goodDetails
AlertManager is a stateful service, and as such needs a writable
location for its data. Using the `StateDirectory` service unit
directive, we can configure systemd to create this directory
automatically, if it does not already exist when the service starts.
In order for the service to be able to write to the state directory, it
must have a stable UID. This means it cannot use the `DynamicUser`
service unit directive.
dustin/metricspi/pipeline/head This commit looks goodDetails
Setting `IPAddressAllow` and `IPAddressDeny` instructs systemd to
construct BPF firewall rules to restrict traffic. Since `vmagent` is
responsible for scraping metrics from hosts on the network, it does not
make any sense to restrict it to localhost-only communication.
None of the Victoria Metrics services should run as a dynamic user.
Indeed, enabling the setting appears to have no effect when `User` is
defined and refers to a user that already exists. To reduce confusion,
we should omit these directives from the unit files.
dustin/metricspi/pipeline/head There was a failure building this commitDetails
*blackbox_exporter* is a generic exporter for Prometheus that can be
used to provide metrics about HTTP, etc. services. I use it to monitor
the availability and responsiveness of websites I host.
dustin/metricspi/pipeline/head This commit looks goodDetails
When I originally added the *victoriametrics* user to the `users` file,
I did not realize that it was possible for a package to define a user.
It makes much more sense to define it there.
There's no reason for these to be separate packages. They come from the
same source tree, so having a single package makes more sense. I only
separated them originally because I wasn't sure exactly how to express
the proper options in the kconfig language.
I think it makes the most sense to install the systemd unit files for
services along with their binaries. This is how most software provided
by Linux distribution package manager works. Providing the systemd unit
with the package eliminates the need for variability, since the paths to
the executable and other files are well defined.
In order to ensure that network interfaces are active, but not
necessarily fully configured, before *network.target* is reached, the
*dhcpcd.service* unit now waits until at least one interface has
processed the `CARRIER` event before being marked as active. This is
accomplished using the *sd_notify* infrastructure, via the
`systemd-notify` command, executed in a client configuration hook
script.
The *dhcpcd.service* systemd unit file that ships with Buildroot is
broken. It orders the unit after *network.target*, which makes no
sense. It also configures the process to fork, but incorrectly
configures the PID file. Finally, by relying on the fork to indicate
that the network is "online," it does not distinguish between "an
interface is up" and "the network is reachable." As most daemons only
need the former, they only rely on *network.target*, and thus can fail
to start correctly.
To correct this brokenness, we provide our own unit file for
*dhcpcd.service*, based on the one included in the Fedora *dhcpcd* RPM
package. For "online" signalling, we provide a pair of shell scripts:
one reads from a named pipe waiting for a message and the other sends a
message to the pipe when configuration is complete.
The *vmutils* package can be built from source easily, as its just a
collection of Go applications. Grafana and Alertmanager are quite a bit
more complicated because of their respective browser applications. In
the interest of getting this project actually going, we'll just install
the official binary releases of these (for now?).
dustin/metricspi/pipeline/head This commit looks goodDetails
Victoria Metrics is not available by default with Buildroot, but adding
a package description for it is very straightforward. The flags and
tags are specified within Victoria Metrics's own Makefile.
Dustin