aw-reporting configuration - log4j/slf4j errors

[Thibault Quillard]

Hi everyone,

I am quite new to the AW API world and wanted to use the github project AW-Reporting to pull the data in my own database. 

However, running the project gives me 3 mistakes : 

1) No appenders could be found for logger / Please initialize log4j properly

2) Failed to load class "org.slfj4.impl.StaticLoggerBinder"

3) Unexpected error accessing the API: Could not open hibernate  Session for transaction

For the first two issues, I have been searching on google and tried to add a logj4.properties file in the class folder, but without luck. 

Would you know what could the problem come from ?

Thanks !

Thibault

[Josh Radcliff (AdWords API Team)]

Hi,

The logging issues (1 and 2) should be non-fatal.  Am I correct in assuming that the process continues after you see those messages?  The Aw Reporting project uses SLF4J, a logging facade that allows you to use whichever underlying logging framework you prefer.  The SLF4J User Manual contains more information on how to configure logging.

Regarding issue #3, the error suggests that you may not have set up your aw-report-sample.properties file with the proper database credentials.  Does the aw-report-sample.properties file you are passing as the -file argument contain valid database connection information as described in the Configure AwReporting section of the README?

Cheers,

Josh, AdWords API Team

[Thibault Quillard]

Hi Josh, 

Thanks a lot, this was indeed a mistake in the database setup !

(PS : I think I've answered to you only on another message by mistake : 

I have another issue of Blanks columns and of rounded values for CTR/Avg CPC and a lot of metrics ... ), Does anybody knows where this could come from ?

Thank you

[Josh Radcliff (AdWords API Team)]

Hi,

The blanks in some columns may be because those columns are not included in the field list for the report in your properties file (see sample file).  If you modify your file to include the fields that are currently blank (such as AdNetworkType1, AdNetworkType2) then you should see the corresponding columns populated in your database.

Regarding the numeric values -- are you sure they are being rounded?  The money amounts are most likely formatted in micros as described here.

Regards,

Josh, AdWords API Team

[Josh Radcliff (AdWords API Team)]

Hi,

A colleague of mine pointed out that in AwReporting, they always disable reporting money in micros here:

https://github.com/googleads/aw-reporting/blob/master/aw-reporting/src/main/java/com/google/api/ads/adwords/jaxws/extensions/downloader/AdWordsSessionBuilderSynchronizer.java#L37

The rounding suggests that there may be a data type mismatch between your DB and the report fields.  Are you still seeing rounding issues?

Thanks,

Josh, AdWords API Team

[Thibault Quillard]

Thanks a lot Josh, that was it for the missing data field ! 

However for the rounded values, I still have an issue : I have copied an extract of my dataBase : 

As you can see, the conversion Rate here is clearly rounded (3 clicks, 33% (and not 33,33%) of ConvRate. 

Live edit, looking at your last answer : The dataBase looks well configured with the conversionRate in "decimal(19,2)"  

[Thibault Quillard]

I've tried the "double" type in my DB for conversionRate but without more success.

[Josh Radcliff (AdWords API Team)]

In that case, could you file an issue on github?  The maintainers of AwReporting will need to look into this in more detail.

Thanks,

Josh, AdWords APi Team

[Thibault Quillard]

Actually, I see now that another person from Brazil had the same issue and had filed an issue on GitHub : https://github.com/googleads/aw-reporting/issues/27 . 

Looks like this is an issue with the locale variable! 

Thanks a lot for your support Josh ! I'll continue on the thread : https://github.com/googleads/aw-reporting/issues/27 

Le mardi 22 avril 2014 10:31:21 UTC-3, Josh Radcliff (AdWords API Team) a écrit