Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Tip: Proxmox backup server backup status monitor (External Table)

Tip: Proxmox backup server backup status monitor (External Table)

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 14.0k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • H
    H
    Hanfelt
    wrote on last edited by
    #1

    This one is not finished but this is a first draft πŸ˜‰

    In agent configuration on the node add this:

    [ExternalTable/PBSBackup]
    Command = proxmox-backup-manager task list --all --output-format json-pretty | jq -r '(map(keys) | add | unique) as $cols | map(. as $row | $cols | map($row[.])) as $rows | $cols, $rows[] | @tsv'
    Separator = \t
    InstanceColumns = Index
    Description = Proxmox backup server status
    PollingInterval = 320
    

    Do a restart agent and then a config poll.

    After that you should be able to go to Data Collection Configuration on that node and add a new Table.


    pbs2.png

    pbs1.png

    1 Reply Last reply
    0
    • D
      D
      Dawid Kellerman
      wrote on last edited by
      #2

      Thank you for the Draft !
      If this is your first timeΒ  πŸ˜‰

      You will need to install on your Proxmox Backup Server

      apt install jq

      ELSE you will get this in the Last Value on PBSBackup

      thread 'main' panicked at 'failed printing to stdout: Broken pipe (os error 32)', library/std/src/io/stdio.rs:1187:9
      note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

      If you try the command on the command line
      PVE-PBS-Server# proxmox-backup-manager task list --all --output-format json-pretty | jq -r '(map(keys) | add | unique) as $cols | map(. as $row | $cols | map($row[.])) as $rows | $cols, $rows[] | @tsv'

      -bash: jq: command not found
      thread 'main' panicked at 'failed printing to stdout: Broken pipe (os error 32)', library/std/src/io/stdio.rs:1187:9
      note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

      Regards Dawid

      1 Reply Last reply
      0
      • H
        H
        Hanfelt
        wrote on last edited by
        #3

        Thanks for the update Dawid πŸ˜‰

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better πŸ’—

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups