MORE THAN EXCEPTION REPORTING
Review each section below to learn more about how PreEmptive Analytics for Team Foundation Server can help streamline feedback driven development, improve software quality and user experience and increase development efficiency.
Application owner and end-user security and privacy have been a central theme of PreEmptive Analytics design and development since its inception. In every case, runtime data collected for management and analysis is owned by the development organization. PreEmptive Solutions has no access (other than is required to ensure the proper functioning of the managed service) and no rights to reuse runtime data. All data transmitted from an application to an endpoint is first encrypted before transmission. Our instrumentation can automate and enforce your opt-in policy, further; you can customize the dialogue and/or the logic. For more information see our Privacy and Security Fact Sheet.
- .NET (including WinForms, Silverlight, WPF, ASP.NET, WinRT, Windows Phone 8
- Java (including server client and Android)
- Native Win32/64
Runtime data is streamed to an analytics endpoint that can be installed next to your TFS instance, on a secured sever or on Microsoft Azure.
Applications can be instrumented in minutes with little or no programming and no agents to manage in production. From cloud to desktop, mobile to back office, your team can have access to incident data without interrupting your current development schedule.
Each organization and application has its own definition of software quality, user experience and operational impact. Our unique and extensible subscription framework automates application and team-specific rules to intelligently automate incident reporting.
Sample implementation leveraging Dotfuscator for instrumentation and an on-premises implementation of the manage and subscribe services.
- Leveraging Dotfuscator, exception tracking is injected into a .NET assembly.
- Once deployed, production apps push runtime data to an on-premises endpoint.
- The endpoint manages and publishes the runtime data via a web service.
- The Subscription service tests its rule inventory against one (or more) endpoints and triggers events as defined by its subscriptions.
- Work items are automatically created and updated accordingly.