11/30/21 Release Notes

​

Maintenance - Data Migration Script (on-premise to cloud)

​

Description

Built a script to migrate Germain data from on-premise to a cloud for these three clients that moved to our AWS cloud. Please reach out to us if you need this script.

​

Maintenance - Engine Installer

​

Description

An installer is now available and automates the installation of a Germain engine. Engine Deployment Reminder: since 8.7.16 Germain engine automatically upgrade themselves. All you need is to ensure they are running for this auto-upgrade to kick in.

​

Maintenance - Other enhancements and bugs (11/30/21)

Below is the list of minor Enhancements and Bugs we have resolved this month. Contact us to get more details. Note that this list does not include the configuration work, or data science help we provide to clients which is tracked on our support site: https://germainux.atlassian.net/servicedesk/customer/portal/1

​

Tip - Find & Solve the most critical UX errors

​

Description

How to spot the UX errors that are -critical- to your business, out of the thousands of useless errors that occur every day and don’t affect your business.

​

Solution

Let us share our 20 years experience troubleshooting UX issues and show you how you can save significant business impact, in minutes or days instead of weeks or months of not knowing, guessing, applying workarounds, etc. The following works for any app e.g. Homegrown, CRM, D2C, ERP, mobile, desktop, etc

1. Find the error that affected Users the most
   • Log onto Germain workspace, go to [User Experience] dashboard (or whatever dashboard that shows metrics on [User Error] kpi or equivalent)
     
   • Look out for the User Errors that affected users the most
     
     Note: remember these are all customizable…and there are different ways to configure Germain so it reports on errors that affect Users, and keep all the other app/infra/network… errors out. That configuration varies depending on the monitored application, as always. If you aren’t sure, just ask us.
   • Drill through on the most impactful errors
     Here, 123 errors lost their connections to their app on that day.
     
2. Find the scenario that lead to each critical error
   • Collect the Reproduction Scenario by replaying these 123 user sessions
     • Example with Siebel CRM app
       
     • Example with React/NodeJS app
       
   • note: in 01/31/22 release, you will have flags helping you identify “new” issues as opposed to issues that occurred before e.g. out of these 123 users that lost their connection to that app, you will be able to tell how many of these were “unique/different” problems.
3. Identify the root-cause
   note: this RCA screen has to be customized for each technology/app.
   • Example with Siebel CRM app
     
   • Example with React/NodeJS
     
     
4. Implement the code/script/object-level recommendations(provided by germainCRT; but all above metrics are provided by germainGermain)
   • Example for Siebel CRM app
     Review the code/object/scripting issues and recommendations that germainCRT found for a severe User Error identified by germainGermain
     
     
     

Note: germainCRT can customized any technology/app, that you would like automate code/object/scripting review and tuning recommendations based on your vendor and your own coding/object/scripting best-practices.

​

Tip - Proactive & Smarter Monitoring

​

Description

This client wanted to proactively and intelligently monitor and resolve failing web servers in a complete automated way, with no team involvement.

​

Solution

• Proactively monitor 10 different URLs (via synthetic http transaction)
  • Add 10 web servers in Data Sources (Germain workspace > left menu > Data Sources)
    
  • Add 10 “http scenarios” (Germain workspace > left menu > wizard > Http Scenario Component Deployment)
    
    
    
    
  • Setup a single KPI to match the synthetic transactions generated by the HTTP monitors. (Germain workspace > Analytics > KPIs; Add New Configuration)
    
  • Create a fact-based SLA to color individual synthetic transactions based on success / failure state:
    
    
• Alert when 3 of these URLs fail
  • Create an aggregate SLA to trigger when 3 or more servers are not reachable. The schedule of the aggregate SLA should match the one selected for the HTTP monitors (for example, if your monitors connect every 5 minutes, also evaluate the SLA every 5 minutes):
    
    
    
• Automate creation of a ticket in ServiceNow
  • Select your SNOW HTTP Action as part of the final step to be executed if there are 3 or more failures:
    
• Auto-restart the 3 failing web servers
  • Once the SLA has been created, you can set up an action to restart the web servers in case of failure. (Germain workspace > Automation > SSH; Add New Configuration)
    
    

​

Get Help

The content of this document is proprietary to GERMAIN SOFTWARE.