You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
name: "CPUUtilization"
unit: "Percent"
statistics:
- Average
===================================================
When I try to run cloudwatch-sender send_metrics /opt/config.yaml --region=us-east-1 --access-key-id="ACCESSKEY" --secret-access-key="secret"
I get the below error :
/usr/local/share/gems/gems/aws-sdk-core-3.89.1/lib/aws-sdk-core/param_validator.rb:33:in `validate!': parameter validator found 2 errors: (ArgumentError)
expected params[:filters][0][:values][0] to be a String, got value nil (class: NilClass) instead.
expected params[:filters][1][:values][0] to be a String, got value nil (class: NilClass) instead.
Could you please help me fixing this error ?
Also I would like to know is it possible to send metrics to Influx Cloud ? If yes, what are the changes required in config files?
The text was updated successfully, but these errors were encountered:
Hi Team,
I have installed cloudwatch-sender via gem. I have created the required config.yaml file as below :
metric_prefix: "cloudwatch"
influx_options:
influx_host: "3.9x.xx.xx"
influx_database: telegraf
influx_username: "username"
influx_password: "password"
influx_port: 8086
metric_types:
EC2 Metrics
namespace: "AWS/EC2"
#ec2_tag_key: "Owner"
#ec2_tag_value: "mohag"
metrics:
===================================================
When I try to run cloudwatch-sender send_metrics /opt/config.yaml --region=us-east-1 --access-key-id="ACCESSKEY" --secret-access-key="secret"
I get the below error :
/usr/local/share/gems/gems/aws-sdk-core-3.89.1/lib/aws-sdk-core/param_validator.rb:33:in `validate!': parameter validator found 2 errors: (ArgumentError)
Could you please help me fixing this error ?
Also I would like to know is it possible to send metrics to Influx Cloud ? If yes, what are the changes required in config files?
The text was updated successfully, but these errors were encountered: