Search results

I think that in PBS, assigning permissions to a token really limits the ability to use the token. But not sure, we need to ask Proxmox Staff. Well, or put a couple of experiments with the API :) UPD. To be honest, I haven't studied the PBS API much, only in terms of monitoring. It is even...

Updated readme to indicate that user on whose behalf the token is issued must have the appropriate rights

You have issued a token on behalf of the user backup@pbs , which has rights: DatastorePowerUser . In order for node monitoring to work, you must either issue a token on behalf of root@pam, or give Audit rights to the user backup@pbs.

Let's try to compare PBS and Zabbix settings for me and for you. PBS API Token: Zabbix macros With these settings everything works fine for me.

I don't know how to see node name in Web ui... You can see it in /api2/json/nodes page. I'm not sure if the problem is in this api endpoint, maybe the problem is in the template. What version of pbs do you have installed?

can you try to open /api2/json/nodes in your browser? node name there is in upper case?

Maybe this endpoint need Admin rights to token... #needtest :) I'll watch it in a couple of hours

Try to set Audit permissions to / for your token in PBS Configuraion -> Access Control -> Permissions

Created new template - Proxmox Backup Server by HTTP. https://github.com/ismvru/zbx-tmplt-pbs Sample latest data:

Migrated repo from git.isaev.tech to https://github.com/ismvru/zbx-tmplt-pve

ZBXNEXT-7506 status changed to "Resolved" and i've found template in ZBXNEXT-7506-6.0 branch in Zabbix git (added by commit 93a1f02092ba7d4a3288f08772fabfed0943ccad by Alexander Bakaldin) :) Perhaps the template will officially appear in Zabbix 6.0.3 (according to Fix Version/s in their jira)

Added a comment in Zabbix Jira that in theory they can use my template as the basis for the official template.

The implementation of Zabbix 6 and Proxmox Backup Server is planned at my work for the end of March - beginning of April. Then I will start adapting the template for fresh Zabbix and will make the template for PBS How long the update will take - I can’t say for sure yet, it’s very difficult to...

Hi all! I apologize, I did not appear here at first because of the coronovirus, and then because I was sent on a "business trip" to the border of Russia and Ukraine (these are the disadvantages of working as a system administrator for the government of the country)... The template should...

Fine! If you have any ideas about new functionality or any bugs - write here, I'll try to do something :) At the moment, I have plans to: 1. Mirror repository with this template to github 2. Modify this template for the work needs of my organization, if necessary 3. Maybe post this template on...

Updated the template by adding 2 new macros: {$PVE_FORCE_ID} - Forces virtual machine ID to autodiscover ignoring macro {$PVE_IGNORE_ID} {$PVE_FORCE_STORAGE} - Forces storage name to autodiscover ignoring macro {$PVE_IGNORE_STORAGE} Usage examples: {$PVE_FORCE_ID} {$PVE_IGNORE_ID} = .*...

Great news! About inverting result: 1. Fast workaround You may try to reconfigure template. In autodiscovery open lxc/qemu discovery, go to Filter tab and change "does not match" to "match" in field near macro 2. Slow workaround You may search PCRE documentation in internet and try to...

Now I experimented and wrote a regular expression .* in macros, zabbix did not discover anything. Now I'm experimenting with regular expressions :) Today I will try to understand exactly how zabbix works with regular expressions and write here based on the results of this small research UPD...

I've updated the template to include the ability to filter the generated items and triggers. Now you can add macro {$PVE_IGNORE_ID} and macro {$PVE_IGNORE_STORAGE} containing regexp to filter VM/LXC IDs and storages. Examples: {$PVE_IGNORE_ID} = ^(100\|90[0-9])$ - Autodiscover will include...

Ol, I'll add macro for excluding storages, vms and containers soon. Monitoring failed backup jobs is a good thing, but I haven't yet been able to figure out how to get the status of the last run of a backup job from the API. So far, a workaround has been implemented. Since PVE writes about...