Skip to main content

Core Concepts

Key terms and definitions

Next

Continue to next page

Overview

GermainUX connects monitoring, analytics, AI, and automation across users, business workflows, applications, and technologies. This reference explains the core concepts used throughout GermainUX and how they relate to one another. At a high level, GermainUX follows a continuous operational model:
ObserveAnalyzePrioritizeActValidate
The concepts below support different parts of this lifecycle. For example: Use this page as a reference when configuring or interpreting GermainUX.

Core Concepts

AA Unit (Analytics & Automation Unit)

Represents the fundamental unit of consumption within GermainUX, tied to either: AA Units are categorized (e.g., events, availability, latency, transactions) and consumed based on usage, enabling flexible and scalable deployment. More details on AA Unit.

Automation

A framework that enables GermainUX to detect, prevent, or resolve issues automatically through: Automation bridges insight → action, reducing manual intervention and accelerating resolution. More details on Automation.

Business Process / Workflow

A sequence of structured activities performed by users, systems, or both to achieve a business goal (e.g., checkout, onboarding, customer support). GermainUX monitors: This enables optimization of both user experience and operational efficiency. More details on Business Process monitoring and insights.

Correlation

The ability to connect and relate multiple entities within GermainUX, such as: Correlation is key to root-cause analysis (RCA), allowing users to understand why an issue occurs, not just what happened. More details on Correlation.

Dashboard

A configurable workspace composed of multiple portlets that provides a consolidated view of performance, insights, and alerts. Dashboards can be tailored for: They serve as the primary entry point for analysis and decision-making. More details on Dashboard.

Datasource

Any system or technology from which GermainUX collects data, including: Datasources enable GermainUX to provide end-to-end visibility across business and technology layers. More details on Datasource.

KPI (Key Performance Indicator)

A measurable indicator used to evaluate performance across business, UX, process, or technical dimensions. Examples: KPIs are the foundation for monitoring, alerting, and optimization. More details on KPIs.

Portlet

A visual component within a dashboard that displays one or more KPIs. Portlets: They are the building blocks of dashboards and drive exploratory and guided analysis.

Focused Flow (User Journey Analysis)

A visualization that highlights the most impactful user paths leading to: It helps identify:
  • Where users succeed
  • Where friction occurs
  • Which paths drive the most business impact
This is a key component of conversion optimization and journey analysis.

Prompt (AI Prompt)

AI prompts are either preconfigured or created on demand to: Increasingly, prompts are agentic, enabling GermainUX to not only analyze but also act (e.g., notify users, fix issues, update systems). More details on AI Prompt.

AI Recommendations

Automatically generated guidance based on analyzed data, sessions, and patterns. They provide: AI Recommendations help teams move from data → decision → action faster. More details on AI-driven Insights & Recommendations

Evidence (Session, Logs, Traces)

Direct, verifiable data supporting an insight or issue, including: Evidence ensures that all insights are trustworthy, explainable, and actionable.

Session Replay

A real-time recording of user interactions (clicks, navigation, behavior), allowing teams to: GermainUX enhances session replay with automated insights extraction. More details on Real User Monitoring/Recording & Session Replay.

Alert

A real-time notification triggered when: Alerts can include: They enable proactive issue detection and response. More details on Alert.

Rule

A configurable logic layer that defines how GermainUX: Rules can power: More details on rules for analytics and for automation.

SLA (Service-Level Agreement)

Defines expected performance thresholds (e.g., uptime, latency, response time). GermainUX monitors SLA compliance and: More details on SLAs.

Report

A structured output (PDF, CSV, HTML) summarizing: Reports can be scheduled or generated on demand to support stakeholder communication and decision-making. More details on Report.

Template

Defines how alerts, reports, or dashboards are formatted and presented. Templates ensure: More details on Template.

Workspace

The GermainUX user interface where users: It is designed to support:
👉 Analysis (What is happening?)
👉 Diagnosis (Why is it happening?)
👉 Action (What should we do?)
More details on Workspace.

Next

  • Review the types of real-time Insights you can get with GermainUX
  • Review GermainUX’s preconfigured integrations and capabilities across supported applications, frameworks, databases, operating systems, infrastructure, and enterprise technologies.
  • Check the other real-time automation (alerting, predicting, reporting, resolving, etc.) you can enable with GermainUX
  • And last but not least, check our Compliance and Security program.

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.