04/30/18 Release Notes

​

Flow Portlet enhancements (for User Behavior and Business Process real-time analytics)

​

Description

This “flow” portlet has been generating a lot of interests, so we are spending more time on making it as useful as possible. This is now exceeding the benefits offered by Google Analytics. Added: Tooltip, Dropoff, Drilldown from within the graph, etc Also significantly improved the performance of that flow graph. (we purposefully reduced the font/hidden some of the text on that below screenshot…but note that there is a Zoom in/out feature that is available to increase/decrease that graph/text)

​

Dropoffs now supported for flow porlet (reporting Business Processes, User Behaviors)

​

Description

​

Flow portlet support for IE and Edge

​

Description

​

XLS export from any portlets and any dashboard

Description XLS export was available on some of the portlets and some of the dashboards but now all, now any data displayed on any portlet and dashboard, can be exported into XLS file. By default 50MB max dataset can be exported into a XLS file but that is configurable. e.g. some customers needed to export the analysis that Germain does of the siebel FDR files, into an excel file..this is now supported for this portlet and any others.

​

Need to export a file larger than 50MB?

If you need Germain users to be able to export files larger than 50MB, you can modify that file: File: {germain service directory}/config/``query-services.yml Parameter: query: maxPost:`` {value in bytes}

​

Added “business object” level to generic fact types

Description This can be used whenever you need to pull out some business-specific value and store as part of a monitoring data point. In addition, “custom data type” can always be added if you need to store multiple properties. Example use case: store “Guest Registration” type for Siebel UX Views

​

Show “Parent Transaction” & “Parent BP” for BP Step

and again most of these fields are configurable so you can always remove/add..

​

Enhanced query constraint parser to allow in [ list ] expressions

Support for:
dim.level in [ “a string”, “another” ]

​

Analysis portlet with parser constraint on RCA dashboard

is now supported

​

Inter portlet filtering support

​

Pivot/constraint/use it on aggregates

enhanced UX Event’s data in a way that we can pivot/constraint/use it on aggregates. Now we can use “input name”, “click name”, … in constraints/pivots …

​

Formatted text on Extra Info Portlet

so it is easily readable. Strings that are displayed in this Text Portlet are now formatted as JSON. e.g. example showing the output arguments of a siebel workflow process execution

​

Parsed Constraints field is now editable

​

Description

by Germain admin only and readonly for other users as showed below.

​

Config - Self-guidance while configuring germain APM

​

Description

more fields with “auto complete” enabled so you dont have to read any doc to understand what value you could possibly enter on a field, on any of the config console dashboards e.g. two examples: kpi and business process step

​

Fixed a bug on Detail Execution Flow portlet

Initially that portlet was missing data due to some UI resizing element related issue which is now fixed.

​

Fixed bug - agent are now showing up

e.g

​

Fixed bug: pivot values on Pivot dashboard

A configuration of the query service introduced in 8.5 needed to be fixed for proper values to show up.

​

Fixed bug: sorting on analysis portlet

for these use cases:

​

Fixed bug: user location IP now mapped to geo location

​

Added wrappers for germain APM Spring services on Windows

​

Synchronization between germain config and enrichment tables

Added synchronization mechanism between germain config and enrichment tables. You can now configure servers you want to monitor in config console (including details like type, environment, etc.). When we collect a single data point, for some data (ex: UX traffic from browser) we only get hostname, so we need to look up additional properties from a table (enrichment table). No need to manually update that enrichment table whenever you change the config to keep things in sync

​

Data migration scripts for 8.5 upgrade

So you don’t loose any data after upgrade to Germain 8.5 Available for:

• Oracle db
• mySQL db

can be made available for:

​

Get Help

The content of this document is proprietary to GERMAIN SOFTWARE LLC.