Tracking exceptions

monitor.TrackException(exceptionInstance); 

monitor->TrackException(exceptionInstance); 

AppDomain.CurrentDomain.UnhandledException += (s,e) => 
         monitor.TrackException(e.ExceptionObject as Exception); 

Thread.setDefaultUncaughtExceptionHandler(new UncaughtExceptionHandler(){
       @Override
       public void uncaughtException(Thread arg0, Throwable arg1) {
         monitor.trackException(arg1);
     }});

monitor.SendLog("This is a special message"); 

monitor->SendLog("This is a special message"); 

monitor.VersionAvailable += (s,e) => 
     {
       MessageBox.Show("Version " + e.OfficialVersion + " is available"); 
     };

monitor.addVersionAvailableListener(new IVersionAvailableListener(){
     @Override
     public void versionAvailable(VersionAvailableEventArgs args) {
       System.out.println(args.getOfficialVersion());                    
     }});

class NewVersionConsumer : public EQATECAnalyticsMonitor::IVersionAvailableEventHandler
{
private:
void OnVersionAvailable(EQATECAnalyticsMonitor::VersionAvailableEventArgs *args);
};

...

NewVersionConsumer *consumer = new NewVersionConsumer();
monitor->VersionAvailable_add(dynamic_cast(consumer));                    

• Version: By default the instance assumes that the official version of the application can be taken from the version number of the calling assembly (this is only true for .NET applications, for java you need to supply the version explicitly). If this is not the case you should assign the version directly.
• Location: Assign GPS location coordinates to this class to provide fine grained location information. This may be specifically useful for mobile devices with built in GPS.
• ProxyConfig: Control the proxy settings for the outgoing request from the monitor. The monitor will use the system defaults unless otherwise instructed.
• UseSSL: Specify if the data should be delivered using the SSL protocol.
• SynchronizeAutomatically: By default the monitor controls when data is delivered to the servers. However, there may be situations where it makes more sense for you to control when the monitor should attempt to connect to the servers (perhaps you only want to connect when your device is tethered). By setting this property to false you take responsibility and can instruct the monitor to attempt to connect using the ForceSync method call on the monitor.
• ServerUri: The address to the server has a default format which contacts the analytics server. If you whish to point the monitor to another address, you can specifify the address directly.
• StorageInterface: The monitor saves usage statistics between starts in a storage area. A default storage is assigned dependent on the where the monitor is executing, but if you wish to provide a different storage, you could implement the IStorage interface and be responsible for loading and saving data
• StorageSaveInterval: The state of the current usages are peridically saved to the storage area to avoid losing too much information if the application unexpectedly terminates without calling the Stopmethod on the monitor instance. The default interval is one minute.
• LoggingInterface: All calls on the monitor API are safe in as much as they will not throw exceptions if e.g. the server is unreachable. If you would like to receive some of the internal logging from the monitor you can implement the ILogAnalyticsMonitor interface and handle the logging messages as you see fit.
• DailyNetworkUtilizationInKB: If this limit is explicitly specified  the monitor will stop sending data to the servers until the next day. This can be used to limit the bandwidth consumption if your application makes use of e.g. pay-as-you-go data subscriptions.
• MaxStorageSizeInKB: If you have a limited amount of disk storage you can specify that the data stored by the monitor should be limited to a certain size. If limited the monitor will selectively store only the most essential data and discard the remaining data. Note that delivery of data to the servers are still attempted, this property only controls the size written to disk.
• TestMode: This property is intended as an easy way to specify that the monitor is in a testing environment. Currently this have the affect that the new version information received from the servers will take non-published version that you have created into account. This should allow you to test how this information will be processed once the application is indeed published. In the future the behavior of this property may be expanded to include other aspects that support the developers and testers in the integration with the EQATEC Analytics servers and API.