Ad Widget

Collapse

Wildcards in agent config

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • baldymaldy
    Junior Member
    • Aug 2022
    • 2

    #1

    Wildcards in agent config

    This is my first post. Hello everyone

    I am having problems using wildcards under the following parameter in Zabbix Agent2 6.0.6 on RHEL7:

    Code:
    ### Option: Server
    # List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix servers and Zabbix proxies.
    # Incoming connections will be accepted only from the hosts listed here.
    # If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally
    # and '::/0' will allow any IPv4 or IPv6 address.
    # '0.0.0.0/0' can be used to allow any IPv4 address.
    # Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com
    #
    # Mandatory: yes, if StartAgents is not explicitly set to 0
    # Default:
    # Server=
    ​
    I have to add about 30 servers and the amount is a subject to change.
    Example:
    myexampleserver001.com
    myexampleserver002.com
    ...
    myexampleserver*.com

    I tried myexampleserver*.com but doesn't seem to work.
    Any tips? Specifying IP and/or range/subnet is out of question unfortunately. DNS names only.

    Thanks in advance!
    Last edited by baldymaldy; 01-09-2022, 08:54.
  • cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4807

    #2
    What's the reason for so many servers?
    But wildcards do not work there... Either you need to specify all of them or use network range.

    Comment

    • baldymaldy
      Junior Member
      • Aug 2022
      • 2

      #3
      Hi cyber,

      The Kubernetes cluster I'm using has Zabbix backend deployed. I defined the DNS name of ingress in Agent config. This is not enough unfortunately and I'm getting "connection reset by peer" errors.
      The reason is, the actual servers communicating between Zabbix backend and Agents (these are external servers outside of K8s cluster) are K8s nodes.
      The backend can be evicted from one node to another or another replica/pod can be created under different node. Their IP address are a subject to change (like in every other enterprise environment).Waking up one day with a need to change config on 150 hosts might not be the best experience..
      Hence why I wanted to use a wildcard and DNS names.

      But I suppose you already answered my questions and I have to use network range... thank you!
      Last edited by baldymaldy; 01-09-2022, 09:29.

      Comment

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

        #4
        It all again confirms my belief that "anything container" is evil..

        Comment

        Working...