Gonne/nixConfig
1
0
Fork 0
forked from Fachschaft/nixConfig
Code Pull requests Activity

Compare commits

base: Gonne:b2f094547390a914527628137e283871b0ff268c
Branches Tags
Gonne:main
Gonne:kaalut
Gonne:lobon
Gonne:update
Fachschaft:main
Fachschaft:nyarlathtop
..
compare: Gonne:bb93d3aed57f4388a90635d86d945fc4b8a5a9c2
Branches Tags
Gonne:kaalut
Gonne:main
Gonne:lobon
Gonne:update
Fachschaft:main
Fachschaft:nyarlathtop

No commits in common. "b2f094547390a914527628137e283871b0ff268c" and "bb93d3aed57f4388a90635d86d945fc4b8a5a9c2" have entirely different histories.
b2f0945473 ... bb93d3aed5

2 changed files with 0 additions and 41 deletions
Show stats Expand all files Collapse all files

1
nixos/roles/default.nix
View file

@ -3,7 +3,6 @@
imports = [
./admins.nix
./nix_keys.nix
./prometheusNodeExporter.nix
(modulesPath + "/virtualisation/xen-domU.nix")
../modules/impermanence.nix
];

40
nixos/roles/prometheusNodeExporter.nix
View file

@ -1,40 +0,0 @@
{config, ...}:
{
imports = [ ];
services.prometheus.exporters.node = {
enable = true;
port = 9100;
# Aligned with https://git.rwth-aachen.de/fsdmath/server/prometheus/-/blob/main/node_exporter/etc/default/prometheus-node-exporter
# It was compiled along the following steps:
# 1. Does the current Debian release supports the collector?
# 2. Is the collector depracated in the latest release?
# 3. Could you probably use the collected metrics for monitoring or are they useless because they make no sense in our context
# (e.g. power adapter inside a VM, use fibre port connection)?
disabledCollectors = [
"arp"
"bcache"
"btrfs"
"dmi"
"fibrechannel"
"infiniband"
"nvme"
"powersupplyclass"
"rapl"
"selinux"
"tapestats"
"thermal_zone"
"udp_queues"
"xfs"
"zfs"
];
enabledCollectors = [
"buddyinfo"
"ksmd"
"logind"
"mountstats"
"processes"
];
};
networking.firewall.allowedTCPPorts = [ 9100 ];
environment.persistence.${config.impermanence.name}.directories = [ "/var/lib/${config.services.prometheus.stateDir}" ];
}