Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-7521

Zabbix server HA implementation on AWS ECS

    XMLWordPrintable

Details

    • Change Request
    • Status: Open
    • Medium
    • Resolution: Unresolved
    • 6.0.0
    • None
    • Server (S)
    • AWS ECS, using EC2 based resources

    Description

      We use AWS ECS to run a variety of containers in our environment and was pleased to see that Zabbix 6 natively supported high availiability (albeit in an active-standby configuration). We're using the official docker images for this.

      The docker image documentation mentions a few environment flags that could be used to configure the HA cluster in docker. Namely these were:

      {{}}

      ZBX_AUTOHANODENAME=fqdn # Allowed values: fqdn, hostname. Available since 6.0.0
      ZBX_AUTONODEADDRESS variable only. Available since 6.0.0

      {{}}

      The issue we are having is that this is resolving the auto-generated container's hostname, that is not present in DNS and therefore the other Zabbix server cannot communicate with that host.

      As these containers are on an ECS cluster, they can reside on any host so hardcoding values as an environment variable isn't an option.

      It would be good if there was a way that the Zabbix server could establish the other servers' status without having to communicate with it via TCP/IP. Ideally just using the database etc.

      Attachments

        Activity

          People

            wiper Andris Zeila
            rhino94 Ryan Launchbury
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: