Icon

Comments have been closed on this page. Please use AppMon & UEM Open Q & A forum for questions about this plugin.

Overview


The Google Analytics Monitor plugin enables querying values from any website monitored with Google Analytics.The plugin retrieves values such as PageViews, Vistors, New Visitors, Bounces, Exits, Time on Page and Time on Site. This plugin allows you to view and correlate these values with application or infrastructure measures collected by dynaTrace.
Correlating these values allows you to answer questions like: Is the Bounce Rate going up because I have a problem on my landing pages? Do my PageViews go down because of slow performance transactions?

The illustration on the left shows a dashboard that shows results from 4 Google Monitors. 2 Monitors monitor blog.dynatrace.com - 2 monitor community.dynatrace.com. One of these monitors uses DELTA mode - the other always retrieves the latest full data entry.

Plugin Details

Plug-In Versions

Google Analytics Plugin (compatible with dynaTrace >= 5.5)
Google Analytics FastPack with pre-configured Dashboard and System Profile

Author

Andreas Grabner (andreas.grabner@dynatrace.com)

dynaTrace Versions

dynaTrace >= 5.5

License

dynaTrace BSD

Support

Not Supported

Known Problems

 

Release History

2010-07-27 Initial Release

Provided Measures

The following image shows the metrics that the monitor provides:

Configuration Oracle Monitor

The monitor requires the following configuration settings:

  • Google Account Name: The Google Account that has access to Google Analytics Data
  • Google Account Password: The Google Account password
  • Website: The website that you want to monitor. You can monitor multiple websites with a single Google account. Default is to monitor the first registered website
  • Return Last Data Entry: If true - the last full data entry value is returned as result. If false - the delta value to the previous retrieved value is returned. The Delta allows you to get metrics as they come in. Google provides data as granular as one hour. If you specify Last Data Entry you will always get the current total number of the current hour.
  • Include Hours: If true - the plugin retrieves values with hourly granularity. This setting only has an impact if you specify Return Last Data Entry = true.
  • Log Detailed Analytics Data: if true - the monitor will log all retrieved measures from the Google API to the monitor log

Installation

Import the Plugin into the dynaTrace Server. For details how to do this please refer to the dynaTrace documentation.

Troubleshooting

When running the Plugin to retrieve Delta values (Return Last Data Entry = false), and the schedule you execute the monitor is to frequent it is possible that there is no new data available from Google Analytics. In this case you may not see values coming in from the monitor on every scheduled monitor interval. Open the Tasks/Monitors Dashlet and check the details of the monitor execution. It will indicate if there was data available or not:

If there are problems with the account credentials or with the web site name please have a look at the monitors log output. Change Log Detailed Analytics Data to true in order to get additional log output

Feedback

Please provide feedback on this monitor either by commenting on this page or by comments on the Community Plugins and Extensions

Contribution

Feel free to contribute any changes on Github

  1. Anonymous (login to see details)

    I'm getting the following error while trying to use this plugin:

    2012-01-11 09:13:35 INFO [MonitorImpl@Google Analytics Monitor_0] Starting Google Analytics Monitor on with lastEntry=false
    2012-01-11 09:13:36 SEVERE [MonitorImpl@Google Analytics Monitor_0] Error connecting with login URI

    Could you please advise how to get this working?

    Thanks

    1. Anonymous (login to see details)

      Hi

      I assume you have correctly configured the monitor with a Google User Account that has access to Google Analytics? The error message implies that the login failed.
      Seems you have already sent us the support archive. I will have a look at this as soon as I have time. In the meantime:
      a) double check all our monitor parameters
      b) make sure that the Collector that executes your monitor has access to the Google Analytics Web Interface

      Andi

      1. Anonymous (login to see details)

        Thanks Andreas for your reply. 

        a) Parameters are correct
        b) I know the server is behind a proxy. Are there any settings to set in the collector to use that proxy?

        Thanks.

        1. Anonymous (login to see details)

          Check out the Collector Proxy Section in the online documentation: Configure Proxies

          Let me know if this solves your problem

          1. Anonymous (login to see details)

            Proxy Configuration did not solve the issue. Internally we found another way to get it working.

            However I have now the issue, that I can't select a specific website from GA, although I specified it in the configuration. The plugin always selects an other website from GA. Where do I find the exact name of the website?

            Thanks.

            1. Anonymous (login to see details)

              Samuel

              The plugin logs all available websites to the Plugin Logfile during startup. You can access the logfiles through the System Information Dashlet or just pull it up from your local disk. You will find log entries that contain information such as "Account Name", "Profile Name", "Profile Id" and "Table Id". The value that you are interested in is "Profile Name".

              The fallback implementation of the plugin is to use the first Profile (=Website) in case the entered Website doesnt match any Profile Name.

              Let me know if this works

  2. Anonymous (login to see details)

    Hi

    can I use this plugin with urchin instead of analytics?

    Thanks

    1. Anonymous (login to see details)

      The plugin uses the Google Analytics Web Service Interface to query the data. I dont think it will work with urchin. But - feel free to change the implementation. When you download the plugin you also have the source code in the bundle

  3. Anonymous (login to see details)

    Do I have to give the complete URL in the Website or in the Host?

    My site is https://sites.google.com/site/somesite

    And it doesn't seem to work, I get an error.

    If there are multiple sites under the same google account, will it get the stats for each website? How do I specify which site I am interested in?

    Thanks,

    Rajesh

    1. Anonymous (login to see details)

      you need to give the name of the site as it shows up in the Google Analytics Dashboard

  4. Anonymous (login to see details)

    Hello!

    Is the plugin compatible with Dynatrace 6.2? Is it updated to the Currently Google Analytics Authentication? I have installed it, but it fails on the pooling execution because of the following AuthenticationException:

    2015-11-06 16:16:23 INFO [Discovery] Plugin "com.dynatrace.diagnostics.plugin.GoogleAnalytics_1.0.0" was successfully installed.
    2015-11-06 16:16:23 INFO [PluginDispatcher] Installing unsupported plugin Google Analytics Monitor Plugin 1.0.0
    2015-11-06 16:16:36 WARNING [UserPluginManager] com.google.gdata.util.AuthenticationException - Error authenticating (check service name)
    com.google.gdata.util.AuthenticationException: Error authenticating (check service name)
    at com.google.gdata.client.GoogleAuthTokenFactory.getAuthException(GoogleAuthTokenFactory.java:628)
    at com.google.gdata.client.GoogleAuthTokenFactory.getAuthToken(GoogleAuthTokenFactory.java:500)
    at com.google.gdata.client.GoogleAuthTokenFactory.setUserCredentials(GoogleAuthTokenFactory.java:346)
    at com.google.gdata.client.GoogleService.setUserCredentials(GoogleService.java:362)
    at com.google.gdata.client.GoogleService.setUserCredentials(GoogleService.java:317)
    at com.google.gdata.client.GoogleService.setUserCredentials(GoogleService.java:301)
    at com.dynatrace.diagnostics.plugin.GoogleAnalytics.GoogleAnalyticsMonitorImpl.retrieveNextFeed(GoogleAnalyticsMonitorImpl.java:143)
    at com.dynatrace.diagnostics.plugin.GoogleAnalytics.MonitorImpl.setup(MonitorImpl.java:42)
    at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:676)
    at com.dynatrace.diagnostics.sdk.UserPluginManager.b(SourceFile:447)
    at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:285)
    at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:51)
    at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:26)
    at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:190)
    at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:413)
    at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.execute(SourceFile:337)
    at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.a(SourceFile:101)
    at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.work(SourceFile:92)
    at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.executeJobInfo(SourceFile:241)
    at com.dynatrace.diagnostics.scheduling.impl.QuartzJob.execute(SourceFile:45)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
    at com.dynatrace.diagnostics.scheduling.impl.QuartzThreadPool$WorkerThread.run(SourceFile:788)

    Thanks!
    Thiago Bien

    1. Anonymous (login to see details)

      Hi Thiago

      I think this is not about the plugin being compatible with Dynatrace 6.x. Its about the authentication against the Google API breaking. It could be that your Google Account credentials that you provided are not valid or maybe dont have access to that service. It could also be that the Google API has changed in the meantime. I implemented this plugin several years ago and havent updated it in a while. You can find the code on GitHub and see what it does internally. Maybe its time to refresh it. Unfortunately I dont have time in the moment for such a projecdt

      Andi

      1. Anonymous (login to see details)

        Hi Andreas!
        I see your point! I am sure the credentials I entered are valid, so it looks like the problem is that the Google API has changed. I will take a look in the code as you mentioned to see what it does internally.
        Thank you very much for your reply!
        Thiago