[ZBXNEXT-7775] Veeam monitoring integration Created: 2022 Jun 06 Updated: 2024 Apr 10 Resolved: 2023 Feb 08 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Templates (T) |
Affects Version/s: | None |
Fix Version/s: | 6.0.13rc1, 6.2.7rc1, 6.4.0beta6, 6.4 (plan) |
Type: | New Feature Request | Priority: | Minor |
Reporter: | Aleksey Volodin | Assignee: | Evgenii Gordymov |
Resolution: | Fixed | Votes: | 3 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
||||
Team: | |||||
Sprint: | Sprint 96 (Jan 2023) | ||||
Story Points: | 3 |
Description |
It well be nice to have official integration for Veeam. |
Comments |
Comment by Andrea Marconi [ 2022 Oct 07 ] |
It would be nice to have this kind of monitoring |
Comment by Evgenii Gordymov [ 2023 Jan 24 ] |
Available in:
|
Comment by Andrea Marconi [ 2023 Jan 24 ] |
Thank you, I will give it a try soon |
Comment by Aleksandre Sebiskveradze [ 2023 Jan 26 ] |
rockandstone you are very welcome. |
Comment by Natalija Burisina (Inactive) [ 2023 Jan 30 ] |
Documentation updated:
|
Comment by Mickael Martin [ 2023 Feb 02 ] |
Yeah! Great idea! Thank you so much! |
Comment by Ugo Viti [ 2023 Feb 04 ] |
Hi,
first of all, thankyou for this great integration!
I configured the new Zabbix Template and the Veeam Server as documented in https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/veeam/backup_replication_http?at=refs%2Fheads%2Frelease%2F6.2
the Template Macro are configured correctly:
{$VEEAM.API.URL} = https://192.168.1.66:9419
{$VEEAM.USER} = zabbix
{$VEEAM.PASSWORD} = <HIDDEN>
The zabbix user is configured as Veeam Backup Viewer under Users and Roles Veeam Menu
but I get the following error in the logs (Zabbix Server 6.2.7) when I run the Veeam: Get metrics check:
2292:20230204:212326.254 [ VEEAM ] ERROR: Request failed with status code 403: .
Testing the Veeam API via command line works without problems:
curl -s -k 'https://192.168.1.66:9419/api/oauth2/token' -d 'grant_type=password&username=zabbix&password=<HIDDEN>' -H 'Content-Type: application/x-www-form-urlencoded' -H 'x-api-version: 1.0-rev2' | jq . { "access_token": "eyJhbGciOiJSUzUxMiIsImtpZCI6IkQ1QkRBMDU4N0IzRTE5NzE4QkFEQjVGQkMxRjcwRUFENjBFMUZBMTYiLCJ0eXAiOiJKV1QifQ.eyJ1bmlxdWVfbmFtZSI6InN2Yy52ZWVhbSIsIm5iZiI6MTY3NTU0MjA5NCwiZXhwIjoxNjc1NTQyOTk0LCJpYXQiOjE2NzU1NDIwOTQsImF1ZCI6ImFjY2VzcyJ9.WG10UmoBxh-pkA-VS9zYM_Nh5p2PrwjmwYyK9nPCHc2wUu22S95z8T9UzStNxuaaDKKdwSxA68QRNgoXVMXS_u1m8corL7Ar03Tcgq3u-7-8O95qwth0LE8y_ZJ7Gegcdx21rn7bdAj37vIFhCb32q4cku2p0fTOO2sQIEli86wfLab-dnXahunkqL5QnUDfPo5gESoWSFo7kv2r0LtTma_Q6GUHmpL7uMwYWbNiqmbszJZ2PaVBUEmJP4Q6rMtfHxLuSiLGzY8pQe8S1rBs42shcyrP9kRvlnJZZxWrLB4tcXceMrPi1KT3M1nHgnZC_6J9xQL2q8dP5x_3r3Y_2w", "token_type": "bearer", "refresh_token": "eyJhbGciOiJSUzUxMiIsImtpZCI6IkQ1QkRBMDU4N0IzRTE5NzE4QkFEQjVGQkMxRjcwRUFENjBFMUZBMTYiLCJ0eXAiOiJKV1QifQ.eyJ1bmlxdWVfbmFtZSI6InN2Yy52ZWVhbSIsInRva2VuX2lkIjoiMjk1ZjZmNmYtODA1Ni00N2UwLTk5ZWQtY2ZjNDU2ZWQ1NjQ3Iiwic2hvcnRfdGVybV9leHBpcmF0aW9uIjoiRmFsc2UiLCJuYmYiOjE2NzU1NDIwOTQsImV4cCI6MTY3Njc1MTY5NCwiaWF0IjoxNjc1NTQyMDk0LCJhdWQiOiJyZWZyZXNoIn0.C44MHo2g3m5K0OXVFi8GtKy36mGYLYpEocsb5wGwkIZEVqHK-PepcurZL-rS2YPmp0bfTTIV0S8jvRx5kN-cioENJvKqbPPxupBJzwtCK5Wj-FDhTOsnU8r-WNAdf46anGBeyN0rdLCgNIMS2fy88ME7lWXaGlsCnMOQ5iRpUS8e9WhZwr2rWchyuz5PImg88btbzZKky9pNVu-e-OSSaJGzofZp-N0BegUXrJPN6xa3omdKcx5Hhd1viaYHXNjytPKKpK-iWtNqd-ISc3LJqQwa-6yufVuwnBsZ7-RIqITB_JVebWl1IpD5figdJIc3SXNBSdfX2-YdGlLjVhRskg", "expires_in": 900, ".issued": "2023-02-04T21:21:34+01:00", ".expires": "2023-02-04T21:36:34+01:00" }
Only changing the Security Role from Veeam Backup Viewer to Veeam Backup Administrator make it works
Using Veeam Backup Viewer, Veeam Restore Operator and Veeam Backup Operator roles give the same 403 error.
The documentation say:
there is another section for configuring the user permissions as read-only under veeam instead of Users and Roles menu?
This is the wanted behavior? If possible I don't want use a veeam administrator for zabbix.
Thankyou for the support.
Kind regards
|
Comment by Evgenii Gordymov [ 2023 Feb 07 ] |
Hello jin78, You can check Required Permissions Veeam Help Center. Perhaps the Veeam Backup Enterprise Manager by HTTP template is suitable for you, but you must have Veeam Backup Enterprise Manager and there are also limitations there example `You can obtain a collection of jobs if you are logged in under an account with the Portal Administrator role only.` |
Comment by Andrea Marconi [ 2023 Feb 07 ] |
asebiskveradze Apologies for my tardiness, I was unable to review the template due to a heavy workload, but I'll do my best to provide feedback if I can. Thank you for your understanding. |
Comment by Pavel Mlcoch [ 2023 Apr 14 ] |
I've the same problem. For viewer role status 403, for administrator role works. |
Comment by Nicola Mauri [ 2024 Mar 21 ] |
Hi all, the 403 error is caused by the api/v1/services call in the GetMetrics Script item. According to Veeam that method requires Adminstration level privileges. As a workaround you can comment out that call, as outlined here. I couldn't notice any impact of this change, maybe that information is never used into the template. Using backup Administration credential in a monitoring tool is a huge security risk, imho. So I think this template should be fixed to not require it. |
Comment by Marco Hofmann [ 2024 Mar 21 ] |
bitmind Thank you so much for your valuable Feedback. I tried several times to get this template to work, like others in the comments above, and I just couldn't get this template to work. So I dropped the idea of using this, which is sad ;-( I think your comment here will go unnoticed, but you should most definitely create a bug report. Please tell me if you have the time for it, otherwise I might do it, because I want to use this official template, but can't as of now. |
Comment by Andrea Marconi [ 2024 Mar 21 ] |
bitmind starko Thank you very much. I don’t have any additional words to add, but I would like to express that I am eagerly awaiting this feature, in the hope that it will be functional someday. |
Comment by Aleksandre Sebiskveradze [ 2024 Mar 21 ] |
Thanks for your Feedback. Please check ZBX-23060
|