Open marioasabella opened 1 year ago
Hi @marioasabella, you can definitely monitoring recursively within a mount point - see Config examples and Secret Configuration
Regarding monitoring all the mount paths, aside from the extra logic required (filtering down to secret engine), I'm not sure its a good general use case to support, as it requires giving VAPE rather broad access to mount points.
If it makes sense for your use case to have that level of access, maybe cronjob that spits out a config.yaml
with the latest mount points would make more sense?
Hi @eugene-davis,
Is there any way to get metadata for everything(mountpoints/secrets) without specifying every single mount point and secret path? We have a vault service with multiple mountpoints and secret paths. It is a big overhead to maintain every new mountpoint and config which is created by users and mirror it to the vault-assessment-prometheus-exporter config.yaml.