TrackFeature doesn't appear to be working

7 posts, 0 answers
  1. Guest
    Guest avatar
    506 posts
    Member since:
    Feb 2012

    Posted 26 Apr 2013 Link to this post

    Hi I am having problems getting TrackFeature to work see code below As you can see something not quite right. Neither Track Usage or Log Messages coming through to Dashboard. Also, quick question how soon should you expect exception reporting to be at the website. Jim Steele Senior Developer T +44 (0) 131 477 8251 Head Office | 24 Forth Street | Edinburgh | EH1 3LH | www.zonal.co.uk (http://www.zonal.co.uk/) Company number SC069596 | Registered in Scotland | 24 Forth Street, Edinburgh EH1 3LH
  2. Guest
    Guest avatar
    506 posts
    Member since:
    Feb 2012

    Posted 26 Apr 2013 Link to this post

    Hi Jim, Just a quick reply. Our technical staff is out of office today - national holiday. Have you tried to click on "live" bottom right corner along with "14" and "60" for day selection. This will show data received the latest 3 days. Hope this will help you! Otherwise we'll get back to you Monday and figure out what the problem is. Best regards, Eigil Rosager Poulsen EQATEC Team
  3. Guest
    Guest avatar
    506 posts
    Member since:
    Feb 2012

    Posted 26 Apr 2013 Link to this post

    Yes done all that, I have exceptions coming through but nothing on the feature tracking or log messages. Cheers JimS
  4. Guest
    Guest avatar
    506 posts
    Member since:
    Feb 2012

    Posted 26 Apr 2013 Link to this post

    Hi Jim, All data, apart from exceptions, for a given day is accumulated and presented the netxt day. So today Monday 29/4 you can see data from yesterday Sunday 28/4 and earlier, but not from today itself: the data from 29/4 will not be show up on the dashboard until tomorrow. That is, except for exceptions: they will show up immediately. I agree that this could be somewhat confusing, as you are lead to believe that the other data is not coming through. We have added, but not yet released, a way of monitoring incoming data that can make up for this lack of immediate feedback that you're missing as a developer when you add new feature-tracking etc and don't see the data appear. Does this make sense and explain the behavior you're seeing? I can see that you have recorded some feature timing and log messages on your product now. best regards, Richard Flamsholt EQATEC Team
  5. Guest
    Guest avatar
    506 posts
    Member since:
    Feb 2012

    Posted 26 Apr 2013 Link to this post

    Can't agree with you there I am seeing data from today for Log messages Feature Values Feature timing as well as exceptions It seems to take between 5mins and 1hr to come through
  6. Guest
    Guest avatar
    506 posts
    Member since:
    Feb 2012

    Posted 26 Apr 2013 Link to this post

    Hi Jim, Sorry, my bad: I had not noticed that the "live" option was enabled for your account. In that case you're right, you will see the data immediately. You're right in saying that your product (JWSTest) is receiving feature values and timings, but no plain feature uses. I can verify this by looking at the content of the received sessions (in the Session view). It can be rejected for a number of reasons, but most conditions would also block feature timings - like, if you call TrackFeature before calling Start, or attempt to track an extraordinary long name, longer that 1000 characters by default. The best way to figure out what's going on is to add debug logging to the monitor. You ca do this by creating the monitor not just from a productID, but from an entire settings-object in which you set a logger. Something like this: IAnalyticsMonitorSettings settings = AnalyticsMonitorFactory.CreateSettings("productid"); settings.LoggingInterface = AnalyticsMonitorFactory.CreateTraceMonitor(); IAnalyticsMonitor monitor = AnalyticsMonitorFactory.CreateMonitor(settings); When you run your app this way, it will print output about monitor actions and errors using Diagnostics.Debug.Write, which means that it will end up in the Debug-window if you run your app inside Visual Studio, or you can capture it using a utility such as e.g. DebugView (http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx). (You can also create your own logger and pass this, if you don't want the output to be directed to the Windows debug-stream). For a successful monitor session you should see log lines such as "Monitor started", "Data sent", etc. If you see any errors related to your feature-tracking it should hopefully point you to the reason. I hope this helps and if it doesn't point to an obvious reason (like "Monitor not started yet", or something) then please write again, and preferably with a small example of the code that doesn't behave as expected. best regards, Richard Flamsholt EQATEC Team
  7. Guest
    Guest avatar
    506 posts
    Member since:
    Feb 2012

    Posted 26 Apr 2013 Link to this post

    It's now working Thanks
Back to Top