Configuring GermainUX Network Monitoring: Response Times, User Quality, and Alerts

⚙️ Configure Network Monitoring

Configure GermainUX network monitoring to define response-time thresholds, user network quality, poor-network detection, dashboards, SLAs, and alerts.

🌐 Monitoring Options

🖥️ Configure Engine-Based Network Monitoring

⏱️ Configure Response-Time Threshold

The Network Monitor Wizard allows you to define a response-time threshold.

For example:

Threshold = 10 seconds

A response time greater than the configured threshold can trigger the associated SLA condition.

Choose a threshold appropriate for the network path and application requirements.

Different targets may require different thresholds.

🔄 Configure Monitoring Frequency

Configure how frequently the Network Monitor executes.

Consider:

• Network criticality

• Required detection speed

• Target availability requirements

• Monitoring overhead

Use shorter intervals for critical connectivity paths requiring rapid detection.

🖥️ Configure Source & Target

A Network Monitor operates between a configured:

Source Server → Target Server

Ensure the selected source represents the network path you actually want to monitor.

For example:

Germain Engine → Application Server

may provide different information than:

Application Server → Database Server

Create separate monitors when multiple network paths require independent monitoring.

🔐 Configure SSH — If Required

When the monitor requires SSH execution, associate the appropriate SSH credentials.

Use credentials with only the permissions required for monitoring.

👤 Configure User-Side Network Monitoring

📡 Enable Poor Network Location

Navigate to:

Germain Workspace → Analytics → UX Monitoring Profiles

Select the appropriate UX Monitoring Profile and enable:

Report Poor Network Location

GermainUX can then identify poor network conditions experienced by users of the monitored application.

📶 Configure Poor Network Grades

GermainUX RUM uses effective connection types to classify browser network conditions.

Available grades include:

• slow-2g

• 2g

• 3g

• 4g

By default or according to your monitoring requirements, define which grades should be considered poor.

For example:

settings.plugins.poorNetworkLocation.poorGrades = ['slow-2g', '2g', '3g'];

With this configuration, slow-2g, 2g, and 3g are considered poor network conditions.

To classify only slower connections as poor:

settings.plugins.poorNetworkLocation.poorGrades = ['slow-2g', '2g'];

Choose the classification appropriate for the application.

A data-intensive application may consider 3g poor, while a lightweight application may not.

📊 Network Grade Data

GermainUX records supported browser-side network information using the user-experience data model.

The Poor Network metric can include:

Type: Browser:Poor Network

Value: Downlink Mbps

Name: Network Grade

Location: Location Dimension

This allows network quality to be analyzed by application, session, user population, and available location dimensions.

📍 Configure Poor Network Location Analysis

Use Poor Network Location telemetry to identify where poor user network conditions occur.

Analyze network conditions by dimensions such as:

• Location

• Application

• User population

• Browser

• Device

• Network grade

This can help distinguish application-performance issues from connectivity conditions affecting a particular population or location.

🎯 Configure SLAs

Configure SLA conditions for network performance that requires operational attention.

Examples:

Target Response Time > Threshold

Target Unavailable

Poor Network Condition Detected

Choose thresholds according to the application and network path being monitored.

Avoid applying the same threshold indiscriminately across all targets and applications.

📊 Configure Dashboards

Create dashboards to analyze network health and its impact on applications.

Examples include:

• Network response time

• Target availability

• Poor network grade

• Poor network locations

• Network-related application performance

• Network performance trends

Where possible, correlate network telemetry with application and user-experience data.

For example:

Application Response Time → Network Grade

or:

Slow Sessions → User Location → Network Condition

🔔 Configure Alerts

Configure alerts for network conditions requiring action.

Examples include:

• Target unreachable

• Response time exceeds threshold

• Repeated network degradation

• Poor network conditions affecting critical users

• Network-related application performance degradation

Configure appropriate:

• Threshold

• Duration

• Recipients

• Escalation

• Actions

Focus alerts on persistent or operationally significant conditions rather than every individual network fluctuation.

⚙️ Configure Automation

Network SLA conditions can trigger configured GermainUX actions.

For example:

Network Monitor → SLA → Alert / Report / Script

or:

Poor Network Detection → Analysis → Alert

Use automation for conditions where an operational response is appropriate.

🧪 Validate Configuration

After configuration, verify both normal and degraded network conditions where possible.

For Engine monitoring, confirm:

• Source and target are correct

• Monitor executes successfully

• Response time is collected

• Threshold evaluates correctly

• SLA and actions operate as expected

For RUM monitoring, confirm:

• Network grade is collected

• Poor-network classification is correct

• Poor Network Location is generated when applicable

• Network telemetry is associated with the correct application and session

ℹ️ Advanced Configuration

Network monitoring can be extended by creating multiple Network Monitors for different source-to-target paths and combining the resulting telemetry with application, infrastructure, and user-experience monitoring.

For user-side monitoring, advanced RUM configuration can be used to adjust the effective network grades considered poor according to the performance requirements of the application.

Please contact us for any help.