[ZBX-25703] doc for Nutanix template misleads on user macros assignment Created: 2024 Dec 09  Updated: 2025 May 07  Resolved: 2025 Apr 28

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 7.0.6
Fix Version/s: None

Type: Incident report Priority: Major
Reporter: Oleksii Zagorskyi Assignee: Aleksandr Kotsegubov
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Causes
caused by ZBX-26368 user macro re-copy during LLD is very... Closed
Duplicate

 Description   

https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/nutanix_http?at=release/7.0
It says that the macros (4 in total) may be set on, quote: "on the host or template level"

The solution consists of 3 templates, where one is main ("Nutanix Prism Element by HTTP") and 2 are used for host prototypes.
Its ok if you set the 4 macros on all the 3 templates, while this is not stated cleanly on the doc.

But if you set the macros only to a main host you created, then LLD discovered hosts do not get the macro value in any way.
So LLD discovered hosts will fail with error "Required param is not set: password." as they do not have the macros.

This solution may require rework or significant improvement in the doc how it should be used.



 Comments   
Comment by Oleksii Zagorskyi [ 2025 Apr 28 ]

As I've reported now ZBX-26368, this could be closed.

Comment by Aleksandr Kotsegubov [ 2025 Apr 28 ]

Will not be fixed.

This is a common approach for all templates with host prototype.

Comment by Brendan [ 2025 May 07 ]

have been banging my head against the wall for hours in regards to this. Have 2 clusters, Prod and DR, as well as Prism server etc.... no matter what I put into the macro's or template directly results in "some" data.. and some errors about password, the best I get out is a few storage container sizes etc.

This really NEEDS to be better documented. Do you add one or all to a host? well you can't add all as they conflict. it really does need better explaining how to use, it the current form it's not that useful... and broken.

Generated at Sat Aug 02 10:50:44 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.