monk-ee / SplunkAppforAWSBilling

8 stars 3 forks source link

File Processing Errors #11

Closed monk-ee closed 8 years ago

monk-ee commented 8 years ago

For example, I see this error. 2016-01-26 17:29:16,449 ERROR ProcessDetailedReport:217 - MERROR - Report File does not exist (IO): [Errno 2] No such file or directory: '/opt/splunk/etc/apps/SplunkAppforAWSBilling/csv/XXXXXXXXXXXXX-aws-billing-detailed-line-items-with-resources-and-tags-2015-10.csv'

I do see XXXXXXXXXXXXX-aws-billing-detailed-line-items-with-resources-and-tags-2015-10.csv.zip in the S3 bucket.

I also see this error. 2016-01-26 17:29:16,783 ERROR FetchDetailedReport:173 - Failed to get file from s3: S3ResponseError: 404 Not Found <?xml version="1.0" encoding="UTF-8"?>

NoSuchKeyThe specified key does not exist.XXXXXXXXXXXXX-aws-billing-detailed-line-items-with-resources-and-tags-2015-01.csv.zip0ED225E3C1CCC3D4b33vC+GG5zBA5uQsRLI2jkbAHarC0jKfZx3BYyC30XM5o9ju4tyMhiVImFiAPtEI3sqH6gHza+k=

I do see XXXXXXXXXXXXX-aws-billing-detailed-line-items-with-resources-and-tags-2016-01.csv.zip in the S3 bucket, I do not have this file for 2015 though.

Any suggestions on where to start troubleshooting this?

monk-ee commented 8 years ago

Supplied Log file:

SplunkAppforAWSBilling.log.txt

monk-ee commented 8 years ago

This error should never have bubbled up anywhere - it is really just informational - the file is not in the bucket. There are legitimate reasons for this.

If the error is continuous, then the wrong ACCOUNT NUMBER has been put in the aws.yaml file.