Skip navigation
1 2 Previous Next 8257 Views 22 Replies Latest reply: Dec 7, 2012 7:08 AM by liondgr8 . RSS
komalgohil Newbie 3 posts since
Jun 6, 2011
Currently Being Moderated

Jun 21, 2011 6:10 AM

ZenAWS not showing Perf Data (Cloudwatch) for any instances

Hi,

 

We're using Zenoss 3.0.3. We have installed the latest ZenAWS zenpack version 1.0.3 and  all instances were detected (from all regions). However, we are not getting any performance graphs of the instances. We have enabled the Cloudwatch. Is there anything else I need to do?

 

Anyone have any ideas regarding this? Any info will be very much appreciated.

 

 

Thanks,

Komal

  • adowds Rank: White Belt 9 posts since
    Jan 22, 2012

    I am having the same problem with zenoss v3.2.1 and zenpack version 1.0.3 on an ubuntu system.  Zenoss finds all of my ec2 instances, and succesfully runs the commands to contact EC2 at regular intervals, but no data is returned nor graphed.  All my instances are in the west coast.

     

    Was there a solution to this problem I missed?

     

     

    Here is the relevant excerpt from my zencommand.log with my aws access credentials removed:

     

     

    2012-01-23 20:11:14,565 DEBUG zen.zencommand: Command: '/bin/sh -c exec /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2Manager -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300'

    2012-01-23 20:11:14,565 DEBUG zen.zencommand: Output: ''

    2012-01-23 20:11:14,565 DEBUG zen.zencommand: Process zencw2.py EC2Manager -u <aws_access_key> -p <aws_secret_key> -r 300  stopped (0), 1.30 seconds elapsed

    2012-01-23 20:11:14,566 DEBUG zen.zencommand: Dropping useless clear event {'manager': 'localhost', 'eventKey': 'zencw2', 'device': 'EC2Manager', 'eventClass': '/Cmd/Fail', 'summary': 'Cmd: /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2Manager -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300 - Code: 0 - Msg: Success', 'component': '', 'monitor': 'localhost', 'agent': 'zencommand', 'severity': 0}

    2012-01-23 20:11:14,566 DEBUG zen.zencommand: The result of "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2Manager -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300" was "''"

    2012-01-23 20:11:14,566 DEBUG zen.zencommand: Next command in 296 seconds

    2012-01-23 20:11:15,537 DEBUG zen.zencommand: Received exit code: 0

    2012-01-23 20:11:15,537 DEBUG zen.zencommand: Command: '/bin/sh -c exec /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2InstanceType -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300'

    2012-01-23 20:11:15,537 DEBUG zen.zencommand: Output: ''

    2012-01-23 20:11:15,537 DEBUG zen.zencommand: Process zencw2.py EC2InstanceType -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300  stopped (0), 1.25 seconds elapsed

    2012-01-23 20:11:15,538 DEBUG zen.zencommand: Dropping useless clear event {'manager': 'localhost', 'eventKey': 'zencw2', 'device': 'EC2Manager', 'eventClass': '/Cmd/Fail', 'summary': 'Cmd: /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2InstanceType -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300 - Code: 0 - Msg: Success', 'component': '', 'monitor': 'localhost', 'agent': 'zencommand', 'severity': 0}

    2012-01-23 20:11:15,538 DEBUG zen.zencommand: The result of "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2InstanceType -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300" was "''"

    2012-01-23 20:11:15,538 DEBUG zen.ComponentCommandParser: ParsedResults

      events: []

      values: []}

    2012-01-23 20:11:15,539 DEBUG zen.zencommand: Next command in 295 seconds

  • dpetzel Rank: Brown Belt 1,141 posts since
    Oct 17, 2010

    I have not used the AWS pack myself, nor do I have an AWS account to test with, but at first glance, these two lines look to be problematic

     

    2012-01-23 20:11:15,538 DEBUG zen.zencommand: The result of "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2InstanceType -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300" was "''"

    2012-01-23 20:11:15,538 DEBUG zen.ComponentCommandParser: ParsedResults

      events: []

      values: []}

     

     

    While logged into the box as the Zenoss user can you manually run the command and see if any more data is presented? Based on the zencw2.py code setting the logging level higher (-v 10) should produce some additional details on what the script is doing

     

     

    '/bin/sh -c exec /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2Manager -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300 -v 10'

  • adowds Rank: White Belt 9 posts since
    Jan 22, 2012

    No, there is no option to increase the logging on the command line as in -v 10. It has already been set to debug level in the config.  And further, nothing is sent to stdout when I execute the command on the console.

  • dpetzel Rank: Brown Belt 1,141 posts since
    Oct 17, 2010

    We are not talking about zencommand, so I'm not sure what config you updated already.

     

    There is certainly an option to increasing the logging on the command line.

    http://dev.zenoss.com/trac/browser/trunk/zenpacks/ZenPacks.zenoss.ZenAWS/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py

     

    59def getOpts():
    60    from optparse import OptionParser
    61    parser = OptionParser()
    62
    63    parser.add_option("-r", "--range", dest="range",
    64        help="time range to poll in seconds ", default=300, type='int')
    65
    66    parser.add_option("-v", "--logseverity", dest="logseverity",
    67        help="desired log level", default=0, type='int')
    68
    69    parser.add_option("-c", "--consolidate",
    70        dest="consolidate", default='Average',
    71        help="Consolidation function (Average, Minimum, Maximum, Sum, Samples)")
    72
    73    parser.add_option("--units", dest="units", default="",
    74        help="units in which data is returned ('Seconds', 'Percent', 'Bytes', "
    75         "'Bits', 'Count', 'Bytes/Second', 'Bits/Second', 'Count/Second')")
    76
    77    parser.add_option("-u","--userkey", dest="userkey",
    78                      default=os.environ.get('AWS_ACCESS_KEY_ID', None))
    79
    80    parser.add_option("-p","--privatekey", dest="privatekey",
    81                      default=os.environ.get('AWS_SECRET_ACCESS_KEY', None))
    82    parser.add_option("-i","--instance", dest="instance",default="")
    83    parser.add_option("--cachefile", dest="cachefile", default=CACHE_FILE)
    84
    85    return parser.parse_args()

    There are several locations in that file with something like:

    if opts.logseverity > 0:

      print something

     

    When you the command I provided above which includes the -v 10 you dont get additional information? The command in question would be:

    '/bin/sh -c exec /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2Manager -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300 -v 10'

  • adowds Rank: White Belt 9 posts since
    Jan 22, 2012

    For those same lines I show the following:

    usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec:

     

    def getOpts():

        from optparse import OptionParser

        parser = OptionParser()

     

     

        parser.add_option("-r", "--range", dest="range",

            help="time range to poll in seconds ", default=300, type='int')

     

     

        parser.add_option("-c", "--consolidate",

            dest="consolidate", default='Average',

            help="Consolidation function (Average, Minimum, Maximum, Sum, Samples)")

     

     

        parser.add_option("--units", dest="units", default="",

            help="units in which data is returned ('Seconds', 'Percent', 'Bytes', "

             "'Bits', 'Count', 'Bytes/Second', 'Bits/Second', 'Count/Second')")

     

     

        parser.add_option("-u","--userkey", dest="userkey",

                          default=os.environ.get('AWS_ACCESS_KEY_ID', None))

     

     

        parser.add_option("-p","--privatekey", dest="privatekey",

                          default=os.environ.get('AWS_SECRET_ACCESS_KEY', None))

     

     

        return parser.parse_args()

     

     

     

    It appears that the advanced logging option was added after the latest stable release? Is there another stable release I should try installing?

  • dpetzel Rank: Brown Belt 1,141 posts since
    Oct 17, 2010

    Really wierd. My installed (3.2.1) has those options in 1.0.3 build of the AWS pack:

     

    [zenoss@localhost ~]$ grep "severity" $ZENHOME/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py

        parser.add_option("-v", "--logseverity", dest="logseverity",

        if opts.logseverity > 0:

            if opts.logseverity > 0:

        if opts.logseverity > 0:

                if opts.logseverity > 0:

                if opts.logseverity > 0:

            if opts.logseverity > 0:

        if stats and opts.logseverity > 0:

     

     

    Are you sure you are looking at zencw2.py and not zencw.py (Without the 2). Your output looks like my version of zencw.py (without the 2), however from your debug output in your original post it indicates is using zencw2.py.

     


  • adowds Rank: White Belt 9 posts since
    Jan 22, 2012

    This is the latest egg release of ZenAWS that I could find:

     

    http://community.zenoss.org/servlet/JiveServlet/download/4423-4-3171/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg.zip

     

    I found it at

     

    http://community.zenoss.org/docs/DOC-4423

     

    Since an egg is just a standard zip file. I just unzipped it and pulled out the zencw2.py file and it's the version without the logging parameter.  Did you install from source or from the distributed egg above, from source, or from another egg?

     

    Thanks!

  • dpetzel Rank: Brown Belt 1,141 posts since
    Oct 17, 2010

    I actually installed via the RPM bundle: http://community.zenoss.org/docs/DOC-3480 so all the core packs were installed as part of that RPM.

     

    Just pulled down that egg from your link as as you've stated its missing the additional options..

  • adowds Rank: White Belt 9 posts since
    Jan 22, 2012

    Oh boy, the good folks at Zenoss released different code in the RPM than

    they did in the EGG for the same version (1.0.3)?  Tell me it's not true!

    :).  My next question is, has anyone who installed the EGG ZenAWS(1.0.3)

    with Zenoss 3.2.1 been successful?  I installed my ZenOss with apt-get and

    the egg by downloading in the link earlier in the thread.

  • dpetzel Rank: Brown Belt 1,141 posts since
    Oct 17, 2010

    Yikes! it would appear that might be the case. I extracted the egg from the RPM, attached if you want to give it a shot

  • Dilip S M Rank: White Belt 8 posts since
    Mar 6, 2012

    I was able to install the zenpack above using the zenoss GUI.

     

    Once I configure the account I am able to get the, instances and instancetype.

     

    but I am not able to get see data of CPU or MEM nor the graph is getting populated.

  • Kali Nguyen Newbie 4 posts since
    Feb 21, 2012

    I have the same problem, what packages should I be installing?

     

    Solaris

  • Michael Speth Rank: White Belt 8 posts since
    Nov 6, 2012

    I also am having the very same problem.  My configuration:

    Zenoss 4.2.0

    ZenAWS 1.1.0

     

    Any ideas on how to fix this problem?  Note, the Zenoss server is in a different time zone from the Amazon Instances.

  • Trey Valenta Newbie 1 posts since
    Nov 28, 2012

    I had a similar problem and, after running a model with verbose logging, discovered that the collection process was timing out. I increased zCommandCommandTimeout and zCollectorClientTimeout to 500 seconds for the EC2Manager device, which finally got things working.

1 2 Previous Next

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points