Using CreateStorage with identifier

3 posts, 0 answers
  1. Kevin
    Kevin avatar
    27 posts
    Member since:
    Aug 2012

    Posted 08 Nov 2013 Link to this post

    Given this line of code:
    analyticsSettings.StorageInterface = AnalyticsMonitorFactory.CreateStorage(EqatecLogsFileShare);

    Three EQATEC files are created at that location named storage_(stuff).bin.  The next time I run the app, all three files are used again.

    Given this line of code that I want to use to support a Citrix environment:
    analyticsSettings.StorageInterface = AnalyticsMonitorFactory.CreateStorage(EqatecLogsFileShare, Environment.UserDomainName + Environment.UserName);

    I end up with three files initially, just like above, and they start with my domain/username to make them distinct from other users.  When I start the app a second time, a second session file is created.  When I start the app a third time, a third session file is created, giving me 5 files total.

    This does not seem to be intended behavior.  This directory will end up with a number of files approaching the number of times the app has been started.  I'm assuming this is a bug?  Do you have a workaround?

    See screenshot for what my EQATEC directory ends up looking like.  The timestamps are off for the two files that don't get duplicated, but that only happened once.  Usually those two do get an updated timestamp.
  2. Kevin
    Kevin avatar
    27 posts
    Member since:
    Aug 2012

    Posted 08 Nov 2013 Link to this post

    UPDATE: I tried this same scenario using the sample .NET application that you can download from the Starter site.  All I did was add a StorageInterface as described above and I ran it on a local, personal machine (no network shares, domain, etc).  The same issue occurs where if an identifier parameter is used, old sessiondata is never deleted.  I'm now convinced this is a bug.

  3. Soren
    Soren avatar
    44 posts

    Posted 11 Nov 2013 Link to this post

    Hi Kevin,

    You should expect to see a new session data file for each start of your application a long with two "static" files that are merely updated. You should also expect to see the older session data files disappearing on new starts of the application, so if that is not the case, this seems like an issue on our part.

    I'll forward this issue to the team and get back to you once we've validate the scenario.

    Thanks for reporting the issue.
    Monitor and track applications built with Icenium at run-time. Reduce support by fixing run-time crashes as they occur, obtain user insights such as location and system configuration, find and remove application bottlenecks, and track which features are used most to help prioritize development.
    Try Icenium with EQATEC Analytics today >>
Back to Top