Cloudwatch input plugin- No Metrics to Query Error in 6.3.0

I'm new to ELK working on new version 6.3.0 I get this error but everything work fine on 6.2.1

Stack: C:/Elastic/logstash-6.3.0/vendor/bundle/jruby/2.3.0/gems/logstash-input-cloudwatch-2.1.1/lib/logstash/inputs/cloudwatch.rb:144:in block in run' C:/Elastic/logstash-6.3.0/vendor/bundle/jruby/2.3.0/gems/stud-0.0.23/lib/stud/interval.rb:20:ininterval'
C:/Elastic/logstash-6.3.0/vendor/bundle/jruby/2.3.0/gems/logstash-input-cloudwatch-2.1.1/lib/logstash/inputs/cloudwatch.rb:141:in run' C:/Elastic/logstash-6.3.0/logstash-core/lib/logstash/pipeline.rb:512:ininputworker'
C:/Elastic/logstash-6.3.0/logstash-core/lib/logstash/pipeline.rb:505:in `block in start_input'
[2018-06-22T09:49:02,442][INFO ][logstash.inputs.cloudwatch] Polling CloudWatch API
[2018-06-22T09:49:02,443][ERROR][logstash.pipeline ] A plugin had an unrecoverable error. Will restart this plugin.
Pipeline_id:main
Plugin: <LogStash::Inputs::CloudWatch namespace=>"AWS/EC2", metrics=>["CPUUtilization"], filters=>{"tag:AppID"=>"APP-691"}, interval=>300, period=>300, region=>"us-east-1", access_key_id=>"AKIAJ4NJJ2HUBWBTLS2Q", secret_access_key=>, add_field=>{"ApplicationId"=>"AWSEC2"}, tags=>["awsec2"], id=>"a5de607fe116e73ef149d651916526bb6a28112496dbd1c5938750a0b84acb54", enable_metric=>true, codec=><LogStash::Codecs::Plain id=>"plain_e5ba9f1f-6d64-4923-b237-0178afe20054", enable_metric=>true, charset=>"UTF-8">, role_session_name=>"logstash", use_ssl=>true, statistics=>["SampleCount", "Average", "Minimum", "Maximum", "Sum"], combined=>false>
Error: No metrics to query
Exception: RuntimeError

input {
cloudwatch {
namespace => "AWS/EC2"
metrics => [ "CPUUtilization" ]
filters => { "xxx" }
interval => 300
period => 300
region => "us-east-1"
access_key_id => "xxxx"
secret_access_key => "xxxxx"
add_field => { "ApplicationId" => "xxx" }
tags => "xxx"
}
}

output {
elasticsearch { hosts => ["localhost:9200"]
index => "awscloud"}
stdout {codec => rubydebug}
}

1 Like

i have the same issue. Could somebody help ?

I have the same issue as well . please help.

@rahulsaini did you solved this problem ??

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.