Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

On puppet 3.0.x, I get an error message from the datadog report processor. #5

Closed
plathrop opened this Issue Jan 20, 2013 · 6 comments

Comments

Projects
None yet
4 participants

Since I've upgraded to 3.0.2, I've been getting an error message from the datadog report processor. Here's the output from puppet with --debug --trace:

Notice: Finished catalog run in 16.60 seconds
Debug: Using settings: adding file resource 'rrddir': 'File[/var/lib/puppet/rrd]{:links=>:follow, :group=>"puppet", :backup=>false, :ensure=>:directory, :owner=>"puppet", :mode=>"750", :loglevel=>:debug, :path=>"/var/lib/puppet/rrd"}'
Debug: Finishing transaction 69891384984120
Debug: Received report to process from instance5.zicasso.com
Debug: Processing report from instance5.zicasso.com with processor Puppet::Reports::Store
Debug: Processing report from instance5.zicasso.com with processor Puppet::Reports::Datadog_reports
Debug: Sending metrics for instance5.zicasso.com to Datadog
Debug: Sending events for instance5.zicasso.com to Datadog
undefined method `[]' for :@aggregation_key:Symbol

robbyt commented Jan 20, 2013

What version of Ruby are you using?

plathrop@server1:~/puppet$ ruby --version
ruby 1.8.7 (2010-01-10 patchlevel 249) [x86_64-linux]

kcampos commented Feb 12, 2013

I am seeing this same issue.

$ ruby -v
ruby 1.8.7 (2011-06-30 patchlevel 352) [i686-linux]
$ puppet --version
3.0.1

at the end of the apply ...

Debug: Received report to process from bio-deploy.local
Debug: Processing report from bio-deploy.local with processor Puppet::Reports::Datadog_reports
Debug: Sending metrics for bio-deploy.local to Datadog
execution expired
execution expired
Debug: Sending events for bio-deploy.local to Datadog
undefined method `[]' for :@msg_title:Symbol
Member

conorbranagan commented Feb 13, 2013

So this was an issue in our Event hashing method within dogapi where it was expecting strings but getting symbols instead of the puppet handler. As a fix, I've updated the dogapi gem to convert all of the arguments to strings before trying to hash (DataDog/dogapi-rb@8a72d2f).

If you update to the latest dogapi gem (1.5.1) the puppet handler should once again work as expected.

kcampos commented Feb 14, 2013

Thanks! Working great now

Tested and working, thanks for the fix!

@cwood cwood added a commit to atlassian/puppet-datadog-agent that referenced this issue Jul 13, 2016

@cwood cwood Merge pull request #5 from lcosmes/lcosmes/add_check_freq_setting
Add check_freq setting
48ace4a

@ardrigh ardrigh pushed a commit to ardrigh/puppet-datadog-agent that referenced this issue Jan 20, 2017

@quiffman quiffman Merge pull request #5 from GeoNet/staging
Upmerge Staging changes to Production
5c01a4b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment