Hung Browser Session real-time detection
Monitoring & Analytics
Static Resource performance insights
Monitoring & Analytics
Synthetic Transaction
Automation
JS script optimization (used for User Monitoring & Replay)
Maintenance
Monitoring & Analytics - Hung Browser Session real-time detection
Description
Ability to detect, in real-time, a hung browser session. Each Browser Event captures a duration in which the main page thread(of the browser) is continuously busy (either due to long-running script, infinite loop, etc).That feature works for any web application (AngularJS, React, Salesforce.com, Siebel, etc).Monitoring & Analytics - Static Resource performance insights
Description
Enhanced monitoring of Static Resource on a web page (applies to any javascript application e.g. AngularJS, React, SalesForce.com, Siebel CRM, etc)Automation - Synthetic Transaction
Description
Enhanced our current Synthetic Transaction mechanism to support a complex user scenario that goes through any given business process.Important Note
Rely on Chrome to run as a headless browser service when you setup a synthetic transaction/process. Do not use any other browser.Maintenance - JS script optimization (used for User Monitoring & Replay)
Description
Significantly reduced the impact of Germain’s JS script on the end-user of the monitored application (Germain’s JS script monitors and analyzes web application user experience such as AngularJS, ReactJS, SalesForce.com, Siebel CRM, WordPress, etc). Impact is now between 2 and 10% (used to be ~15-30%). That optimization applies to any web application on any browser. That 2-10% impact was valided/tested against Siebel CRM OUI IP15 and IP17, and using these browsers: Chrome, Edge, Firefox, IE, Safari. A reminder that it is always recommended to test/assess the impact of any monitoring tool (including Germain) before production deployment and adjust monitoring type and frequency taking into account benefit-vs-impact. It is also important to note that the impact will vary from one monitored application to the next and one version of that monitored application to the next, and is dependent on the way that monitored application is built and customized.Get Help
Contact GermainUX Support
The Germain Team can help you set this up.
Can't find what you need?
Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.
The content of this document is proprietary to GERMAIN SOFTWARE.