Skip to content
Snippets Groups Projects
Select Git revision
  • master
  • gzip_ext
  • debian
  • pristine-tar
  • upstream
  • backupninja.conf.d
  • when-override
  • maethor-master-patch-46063
  • maethor-master-patch-70558
  • expand_pruning_options
  • systemd_integration
  • borg-sftp-support
  • nap-initial
  • mariaback_full-intial
  • borg-ssh-keygen
  • borg-custom-init-options
  • stretch-backports
  • backupninja_debian/1.2.2-1
  • backupninja_upstream/1.2.2
  • backupninja-1.2.2
  • backupninja_debian/1.2.1-1
  • backupninja_upstream/1.2.1
  • backupninja-1.2.1
  • backupninja_debian/1.2.0-1
  • backupninja_upstream/1.2.0
  • backupninja-1.2.0
  • backupninja-1.2.0-rc1
  • backupninja_debian/1.1.0-1
  • backupninja_upstream/1.1.0
  • backupninja-1.1.0
  • backupninja_debian/1.0.2-1
  • backupninja_upstream/1.0.2
  • backupninja-1.0.2
  • backupninja_debian/1.0.1-2
  • backupninja_debian/1.0.1-1
  • backupninja_upstream/1.0.1
  • backupninja-1.0.1
37 results

etc

  • Clone with SSH
  • Clone with HTTPS
  • Forked from Liberate / backupninja
    Source project has a limited visibility.
    Micah Anderson's avatar
    micah authored
    This requires that `prometheus-node-exporter` is installed.
    
    If `reportprom` is set, then during the reporting phase, metrics will be written
    to `${prom_textfile_dir}/backupninja.prom`, which will then be available for
    scraping by prometheus.
    
    The metrics simply report the hostname and the number of actions run, the number
    of warnings, errors, fails, and halts that were produced in the backup run.
    
    These are written to the prometheus-node-exporter directory in an atomic way.
    fa2528a0
    History
    Name Last commit Last update
    ..