Ad Widget

Collapse

Azure monitoring - multiple cloned templates required?

Collapse
This topic has been answered.
X
X
 
  • Time
  • Show
Clear All
new posts
  • anslu
    Member
    • Aug 2023
    • 30

    #1

    Azure monitoring - multiple cloned templates required?

    Hello,
    I wanted to confirm if that's expected behavior or I'm doing something wrong.

    Zabbix has been offering Azure resource monitoring for some time now. In general, it works well, though support is still missing for certain resources, like Elastic MSSQL (as part of an Elastic Pool). However, when it comes to monitoring multiple subscriptions, it seems that templates need to be cloned for each one. The issue is that the Azure template is actually a set of linked sub-templates, which adds complexity.

    Click image for larger version

Name:	image.png
Views:	167
Size:	32.7 KB
ID:	504373
    To monitor multiple Azure subscriptions, I need to clone the same templates and fill in the values for each. Then, I have to link sub-templates to the main "Azure by HTTP" template. With 8 subscriptions under single tenant, that ends up being around 100 templates to manage. Keeping them all up to date is especially time-consuming. Am I missing something, or is it just how it works?

    Also, I noticed that sub-templates don’t inherit Enterprise App values from the main template, so I have to copy the same values repeatedly. Is this expected behavior?
  • Answer selected by anslu at 27-06-2025, 14:55.
    cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4807

    yes.. you need to clone them.. But you can also do it on the side, download latest template, change all uuid-s in it (script it), change all those destination host and template and template group names and then import it... we also change all lines where scripts log something to server log... Original has just "Zabbix.log(4, '[ Azure"....." there but we add somekind of handle to be able to distinguish, which set of templates fails ... "Zabbix.log(4, '[ Azure XXXX ]"

    These tempaltes are not linked to each other, so inheritance does not work here...

    Comment

    • cyber
      Senior Member
      Zabbix Certified SpecialistZabbix Certified Professional
      • Dec 2006
      • 4807

      #2
      yes.. you need to clone them.. But you can also do it on the side, download latest template, change all uuid-s in it (script it), change all those destination host and template and template group names and then import it... we also change all lines where scripts log something to server log... Original has just "Zabbix.log(4, '[ Azure"....." there but we add somekind of handle to be able to distinguish, which set of templates fails ... "Zabbix.log(4, '[ Azure XXXX ]"

      These tempaltes are not linked to each other, so inheritance does not work here...

      Comment

      • anslu
        Member
        • Aug 2023
        • 30

        #3
        Originally posted by cyber
        yes.. you need to clone them.. But you can also do it on the side, download latest template, change all uuid-s in it (script it), change all those destination host and template and template group names and then import it... we also change all lines where scripts log something to server log... Original has just "Zabbix.log(4, '[ Azure"....." there but we add somekind of handle to be able to distinguish, which set of templates fails ... "Zabbix.log(4, '[ Azure XXXX ]"

        These tempaltes are not linked to each other, so inheritance does not work here...
        Thank you cyber, this was I thought. In case when needed will edit templates from the script end, thank you for suggestion.

        Comment

        Working...