Ad Widget

Collapse

Monitoring EC2 nodes from outside of EC2

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • bugg_tb
    Junior Member
    • Oct 2011
    • 1

    #1

    Monitoring EC2 nodes from outside of EC2

    Hi Guys

    I have a bit of an issue I'm trying to solve (and you're talking to an absolute Zabbix newb)

    I have a load of EC2 nodes that spin up and down and I want them to register themselves automatically with my Zabbix server that runs outside of the EC2 world.

    The problem with this is that it appears the Zabbix agent is using my EC2 internal IP, which is invisible to the outside world.

    So in my logs I see a lot of:

    28684:20111021:155524.478 Sending list of active checks to [176.xxx.xxx.xxx] failed: host [puppet] not found
    28696:20111021:155524.953 Item [example:agent.ping] error: Get value from agent failed: *** Cannot connect to [10.xxx.xxx.xxx]:10050 [Interrupted system call]

    Type of things. My IP is 176.x so I know that the top line is correct, but then Zabbix is trying to connect back on the 10.x internal ip which it will never be able to hit.

    I tried setting the SourceIP address and it makes no difference.

    If there anything I can do to bridge the gap or do I have to run a Zabbix proxy or something to make this work?

    Thanks

    Tom
  • Matthieu
    Member
    • Mar 2011
    • 41

    #2
    Hi,

    To monitor aws instances:

    * Install a zabbix proxy.
    * Connect it with your zabbix server (by a VPN: VPN or ssh port forwarding)
    * Install and configure zabbix agents in your instances and build an AWS AMI with the Zabbix Proxy IP in zabbix_agentd.conf). Of course if you launch/terminate the same instance type
    * Use auto registration(action) on zabbix web server(auto discovery is also a solution but it doesn't works for me).


    Matthieu

    Comment

    Working...