Skip to main content
ComponentsEngineJS ProfilerMobile AppRPA Bot RecorderRUM JS
Availability2022.1 or later

Common Outliers

Spotting unusual SAP changes

Configuration Guidelines

Settings for reliable detection

SAP Commerce Cloud

Orders, revenue and browsing

Investigation

Correlating outliers with evidence
Configure Outlier Detection for SAP

​
Overview

GermainUX identifies unusual behavior in monitored SAP applications by comparing current activity with historical patterns or configured thresholds. Outlier detection can be applied to telemetry collected from:
  • SAP Fiori, SAPUI5, Web GUI, and compatible web applications
  • SAP Commerce Cloud storefronts
  • User sessions and business processes
  • APIs and integrations
  • Application logs
  • Hosts, services, processes, and databases
  • Synthetic transactions
GermainUX analyzes data collected through configured monitoring components and integrations. It does not natively profile ABAP code.

​
Prerequisites

Before configuring outlier detection:
  • Deploy the required GermainUX monitoring components.
  • Verify that the relevant telemetry is being collected.
  • Configure the SAP application, business process, or infrastructure KPIs.
  • Collect enough representative data to establish normal behavior.
  • Exclude maintenance, testing, and other nonrepresentative periods.
Depending on the use case, telemetry can be collected through RUM JS, JS Profiler, GermainUX Engine, RPA Bot Recorder, Code Profiler for supported Java services, or custom integrations.

​
Common Outliers

GermainUX can detect unusual changes in:

​
Configure Outlier Detection

1

Open the GermainUX configuration for the relevant KPI, application, or business process

2

Select the measurement to analyze

3

Define the application, environment, transaction, or other dimensions used to group the data

4

Select the evaluation and comparison periods

5

Configure the sensitivity and minimum data volume

6

Exclude maintenance, testing, and known nonproduction activity

7

Save and enable the configuration

The available fields depend on the GermainUX version and the type of telemetry being analyzed.

​
Configuration Guidelines

​
Use meaningful dimensions

Create separate baselines for workloads that behave differently, such as:
  • Production and test environments
  • SAP applications
  • SAP Commerce Cloud sites
  • Business processes
  • Pages, routes, APIs, or transactions
  • Regions and device types
Do not combine unrelated transactions into the same baseline.

​
Require sufficient volume

Configure a minimum number of requests, sessions, errors, or process executions before evaluating an outlier. This prevents low-volume fluctuations from generating misleading results.

​
Account for recurring patterns

SAP activity may vary by hour, day, business schedule, or batch-processing window. Compare similar operating periods when the workload has predictable patterns.

​
Combine outliers with thresholds

Use outlier detection to identify unexpected changes and fixed thresholds to enforce known service objectives. For example, alert when checkout time is significantly above its normal range or exceeds the maximum acceptable duration.

​
SAP Commerce Cloud

For SAP Commerce Cloud, GermainUX can identify unusual changes in:
  • Storefront performance
  • Product searches and no-result searches
  • Product and cart activity
  • Checkout duration and failures
  • Cart and checkout abandonment
  • Conversion rates
  • JavaScript and network errors
  • API and third-party service performance
  • Synthetic browse, login, cart, and checkout transactions
Use authoritative order data for confirmed orders and revenue. Browser events provide insight into the customer journey but should not replace server-side transaction records.

​
Business-Process Outliers

GermainUX can analyze configured SAP business processes when their steps are observable through browser events, logs, APIs, custom events, or synthetic transactions. Examples include:
  • Login
  • Order creation
  • Approval workflows
  • Purchase-to-pay activities
  • Customer-service workflows
  • Browse-to-purchase journeys
  • Cart and checkout
GermainUX can identify abnormal duration, failure, abandonment, repeated steps, or unusual transitions.

​
Investigation

When an outlier is detected, correlate it with available evidence such as:
  • Affected users and sessions
  • Session Replay
  • User actions
  • Browser and JavaScript errors
  • Network requests
  • Application logs
  • API and integration performance
  • Host, process, and database metrics
  • Synthetic transaction results
  • Business-process steps
  • Recent deployments
Cross-system correlation requires compatible timestamps and shared identifiers where available. GermainUX does not automatically create browser-to-ABAP execution traces.

​
Alerts

Configure alerts for sustained or significant outliers. Include:
  • Application and environment
  • Affected transaction or process
  • Current and expected values
  • Number of affected users or transactions
  • Duration and severity
  • Related errors
  • Link to the relevant GermainUX analysis
Prioritize alerts based on business impact, affected-user count, duration, and severity.

​
Validation

After enabling outlier detection:
1

Confirm that the selected KPI receives data

2

Verify the filters and grouping dimensions

3

Check that the comparison period represents normal activity

4

Confirm that low-volume periods do not create false positives

5

Validate maintenance and test exclusions

6

Review detected outliers and adjust sensitivity as needed

7

Verify that alerts reach the correct recipients

​
Troubleshooting

​
No outliers are detected

Verify that:
  • The KPI contains sufficient data.
  • The rule is enabled.
  • Filters are not excluding all telemetry.
  • Minimum-volume requirements can be met.
  • Sensitivity is appropriate.

​
Too many outliers are detected

Verify that:
  • Different applications and transactions have separate baselines.
  • Recurring daily or weekly patterns are considered.
  • Maintenance and test activity are excluded.
  • Minimum-volume requirements are configured.
  • Sensitivity is not too high.
  • Alerts require the condition to persist.

​
Privacy

Do not collect passwords, authentication tokens, payment information, or unnecessary personal data. Apply GermainUX masking, exclusion, access-control, and retention settings to all monitored SAP telemetry.

​
Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your SAP environment. Contact GermainUX Support.

​
Get Help

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

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.