Ad Widget

Collapse

parameterized templates

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mlongtin
    Junior Member
    • Feb 2010
    • 1

    #1

    parameterized templates

    Is there a way to parameterize templates and include those multiple times?

    I want to monitor multiple instances of Oracle running on the same server, I'd like to check the same thing for all of them. Is there a way to include the same template, once per instance, with the instance name as parameter?

    Thanks for your help
  • alixen
    Senior Member
    • Apr 2006
    • 474

    #2
    Hi,

    Originally posted by mlongtin
    Is there a way to parameterize templates and include those multiple times?

    I want to monitor multiple instances of Oracle running on the same server, I'd like to check the same thing for all of them. Is there a way to include the same template, once per instance, with the instance name as parameter?

    Thanks for your help
    I am afraid that it is not possible.
    I hoped that macro feature introduced in 1.8 could be used to do that but I was wrong (see my post http://www.zabbix.com/forum/showthread.php?t=14826).

    I currently clone templates (export/edit XML/import), but it is tedious and I am still looking for a better way.

    Regards,
    Alixen
    http://www.alixen.fr/zabbix.html

    Comment

    • jakub
      Junior Member
      • Feb 2010
      • 3

      #3
      In 1.8 it is still not possible since the keys with macros are not expanded until server actually sends active check list.
      The same is on protocol layer where zabbix server expects responses to have original key - without macros expanded. This makes it impossible to distinguish for which expanded version of the key data is for.

      I have the same problem with JMX. I want to have a generic JMX template with port number defined as macro. If I have more than one services on a single host that I want to link in this generic template for but with different macro value I get this error:

      Code:
          * Template with item key [jmx[{$JMX_PORT},java.lang:type=MemoryPool,name=PS Eden Space,usage,used]] already linked to host
          * Template with item key [jmx[{$JMX_PORT},java.lang:type=MemoryPool,name=Code Cache,usage,used]] already linked to host
      This is serious limitation because it still forces me to use Export-sed-Import trick.

      Comment

      Working...