Ad Widget

Collapse

EC2 and Autoregistration issues

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • nicolasg
    Member
    • Apr 2011
    • 50

    #1

    EC2 and Autoregistration issues

    Hi,

    We have an AWS EC2 environment using HostMetadata for the Autoregistration feature but unfortunately this is causing some serious problems.

    The target nodes are in diverse region locations been monitored through Zabbix Server and Proxy. For existing hosts that we have already manually added through the frontend when they autoregister they will update configuration settings with different interfaces.

    For example as you can see in the image bellow we have node server2.example.net, Zabbix checks the agent using the DNS address. With the autoregistration for this existing host it will add 2 new addresses with it's internal IP address, one from autoregistering to Zabbix Server in the same region and another from autoregistering to the Zabbix Proxy from a different AWS region (there fore different IP/DNS value) :



    This is causing agent's to be unreachable and JVM monitoring not working properly. Is anyone else using Autoregistration along with Zabbix proxy in a EC2 environment ? Did you had the same problems ? Any help on how to fix this ?

    Kind regards,
    N.
    Attached Files
Working...