Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No data received #3

Closed
ghost opened this issue Aug 25, 2015 · 4 comments
Closed

No data received #3

ghost opened this issue Aug 25, 2015 · 4 comments

Comments

@ghost
Copy link

@ghost ghost commented Aug 25, 2015

Hey,

I got problems setting up the input. I tried multiple config variations but I don't receive any data. My latest config looks like this.

Input:

input {
  cloudwatch {
    tag_name => 'monitored'
    tag_values => [ 'true' ]
    interval => 5
    period => 60
    region => 'ap-southeast-1'
    access_key_id => "xxx"
    secret_access_key => "xxxxxx"
  }
}

When running /opt/logstash/bin/logstash -f /tmp/testconfig --debug

I can see, that it pulls the correct instances, but the logstash output instances don't receive anything to process

[AWS CloudWatch 200 0.053 0 retries] get_metric_statistics(:dimensions=>[{:name=>"InstanceId",:value=>"i-xXxXxXx"}],:end_time=>"2015-08-25T13:35:55+00:00",:metric_name=>"CPUUtilization",:namespace=>"AWS/EC2",:period=>60,:start_time=>"2015-08-25T13:35:50+00:00",:statistics=>["SampleCount","Average","Minimum","Maximum","Sum"])
 {:level=>:info, :file=>"aws/core/client.rb", :line=>"410", :method=>"log_response"}

Thanks in advance

@ghost ghost changed the title Does not work for me.. No data received Aug 25, 2015
@ghost

This comment has been minimized.

Copy link
Author

@ghost ghost commented Aug 25, 2015

Seems like a 3rd party problem. @cloudwatch.get_metric_statistics(opts).data doesn't contain any datapoints..

@ghost

This comment has been minimized.

Copy link
Author

@ghost ghost commented Aug 25, 2015

Solution: interval => 5 is too little. For me it does work with interval => 300. I also tried interval => 60, what did not work.
I'm not sure why it's not working with a small value.. Maybe latency, undocumented behaviour, internals... No idea

But yeah, great plugin! Thanks man :)

@ghost ghost closed this Aug 25, 2015
@jrgns

This comment has been minimized.

Copy link
Contributor

@jrgns jrgns commented Aug 26, 2015

@PhilippWoe Glad you got it working :)

I think you have to enable detailed monitoring for intervals smaller than 15 minutes? I might be thinking of another interval, though.

@jrgns

This comment has been minimized.

Copy link
Contributor

@jrgns jrgns commented Oct 13, 2015

At second glance, I think if the interval is too small, the plugin starts fetching new metrics before the previous run completes.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.