For the instance, volume, and EBS usage, the app writes logs into $SPLUNK_HOME/etc/apps/SplunkAppforAWS/log.
Take a look to see if you have any log data in opstmp.txt, final22.txt, ci1.txt, and ebs1.txt. These files are overwritten every time the scripts run. When the scripts are running correctly, here is a sample of the file contents:
opstmp.txt:
05-05-2014 14:29:00 +0000 subaccount=pete region=us-east-1d instanceid=i-12341234
instancetype=m1.small cpuutilization=0 networkin=118 networkout=142
05-05-2014 14:28:00 +0000 subaccount=pete region=us-east-1d instanceid=i-12341234
instancetype=m1.small cpuutilization=0 networkin=42 networkout=28
ebs1.txt:
05-05-2014 14:36:24 +0000 subaccountid=123412341234 region=us-east-1 start_time=2014-01-15T13:11:29.000Z snap_id=snap-12341234 size=35 vol_snapshot_id=vol-12341234 snap_tags=[Name=hpwin-root] stype=S
05-05-2014 14:36:24 +0000 subaccountid=123412341234 region=us-east-1 start_time=2014-03-17T18:49:04.000Z snap_id=snap-12341234 size=8 vol_snapshot_id=vol-12341234 snap_tags=[None] stype=S
ci1.txt:
05-05-2014 14:36:24 +0000 instancetype=m3.medium region=us-east-1b subaccount=pete instanceid=i-12341234 tags=[Name=webtest] uptimedays=60
05-05-2014 14:36:24 +0000 instancetype=m1.medium region=us-east-1b subaccount=pete instanceid=i-12341234 tags=[Name=abc abc-test=DC1] uptimedays=62
final22.txt:
05-05-2014 14:36:24 +0000 instancetype=m3.medium region=us-east-1b subaccount=pete instanceid=i-12341234 tags=[Name=testutm] uptimedays=6 spot=N running=Y reserved=N
05-05-2014 14:36:24 +0000 instancetype=m1.small region=us-east-1d subaccount=pete instanceid=i-12341234 tags=[Name=newdev-test] uptimedays=6 spot=N running=Y reserved=N
Hope this helps,
Pete
... View more