Closed MrDrache333 closed 2 years ago
I'm also experiencing the same but it's just for some clients. 2/15 clients haven't had their friendly_name scraped for some reason.
The notes indicate "all you need to do is to add the friendly name in the comments preceding a peer (and enable the flag since this feature is opt-in)", but what/where is the flag?
The notes indicate "all you need to do is to add the friendly name in the comments preceding a peer (and enable the flag since this feature is opt-in)", but what/where is the flag?
https://github.com/MindFlavor/prometheus_wireguard_exporter#flags-available
_PROMETHEUS_WIREGUARD_EXPORTER_CONFIG_FILENAMES or -n depending on what you use.
@ncabete can you please start the explorer with the verbose flag active, try a scrape and post the log here? Be aware that, unless compiled with rust's leaky_log
compile time flag, no private keys will be displayed but public keys will (if it bothers you, please redact them).
Also note that if you have peers
in the main wireguard file you have to specify it manually in the --extract_names_config_files
file (it's not automatically parsed).
@MindFlavor turns out I just had to clean up my peers config. Everything is working as intended on my side. Thank you
No friendly Names are shown in the scraped metrics but configured as described in the ReadMe. Ive also restarted the service and Docker-Container
Docker-compose:
wg0.conf (1 client)
Metrics: