> ## Documentation Index > Fetch the complete documentation index at: https://docs.germainux.com/llms.txt > Use this file to discover all available pages before exploring further. # Concepts & Terminologies > GermainUX connects monitoring, analytics, AI, and automation across users, business workflows, applications, and technologies. > **[Core Concepts](#core-concepts)** > > Key terms and definitions ## 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: Observe Analyze Prioritize Act Validate The concepts below support different parts of this lifecycle. For example: | Concept | Description | | - | - | | **Facts and [Measures](https://docs.germainux.com/main/display-name-for-kpi-field.md)** | describe what GermainUX collects and measures. | | **[KPIs](https://docs.germainux.com/main/manage-kpis.md) and [SLAs](https://docs.germainux.com/main/slas.md)** | define what matters and when a condition requires attention. | | [**Correlation**](https://docs.germainux.com/main/correlation-and-tracing.md) | connects user, workflow, application, and technology evidence. | | **[Analytics](https://docs.germainux.com/main/analytics.md) and [AI](https://docs.germainux.com/main/ai-settings.md)** | help identify patterns, impact, causes, and opportunities. | | [**Session Replay**](https://docs.germainux.com/main/user-monitoring-and-replay.md) | provides detailed evidence of what a user experienced. | | **Rules and [Automation](https://docs.germainux.com/main/automation.md)** | turn conditions and insights into actions. | | **Alerts and [Reports](https://docs.germainux.com/main/reporting-automatic.md)** | communicate findings to the appropriate teams. | | **AA Units** | measure analytics and automation consumption. | 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: | Type | Details | | - | - | | The measurement of a metric (analytics) | • Consumes AA Units when GermainUX captures, evaluates, or stores metric observations. • Applies to events, availability checks, latency measurements, errors, and user-experience signals. | | The execution of an action or transaction (automation) | • Consumes AA Units when GermainUX performs automated remediation, workflow execution, or synthetic/business transactions. • Scales with action volume, transaction frequency, and monitored automation scope. | 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](https://docs.germainux.com/main/analytics-and-automation-unit-aa-unit.md). ### Automation A framework that enables GermainUX to **detect, prevent, or resolve issues automatically** through: | Mechanism | Details | | - | - | | RPA bots | • Execute repeatable UI-driven tasks across web, desktop, and enterprise applications. • Validate user flows, collect operational evidence, and remediate known failure patterns. | | System actions (e.g., restarting services, updating data) | • Invoke predefined technical operations through scripts, APIs, connectors, or orchestration tools. • Support rapid containment for service degradation, failed jobs, stale data, and integration errors. | | Business actions (e.g., notifying users, triggering workflows) | • Initiate workflow steps such as notifications, ticket creation, approvals, and stakeholder escalation. • Align remediation with business priority, SLA risk, user impact, and revenue exposure. | Automation bridges **insight → action**, reducing manual intervention and accelerating resolution. More details on [Automation](https://docs.germainux.com/main/automation.md). ### 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: | Metric | Details | | - | - | | Completion rates | • Measures the percentage of initiated workflows that reach the defined successful outcome. • Segmented by application, user cohort, region, device, process step, or business channel. | | Time to completion | • Tracks elapsed duration from process start to completion across user and system activities. • Highlights latency, queueing, approval, integration, and manual handling delays. | | Friction points | • Identifies steps with excessive retries, errors, slow responses, rage clicks, or repeated navigation. • Prioritizes optimization opportunities based on frequency, severity, and business impact. | | Drop-offs | • Detects where users or transactions abandon the workflow before reaching the target outcome. • Correlates abandonment with technical failures, UX issues, validation errors, or process complexity. | This enables optimization of both **user experience and operational efficiency**. More details on [Business Process monitoring and insights.](https://docs.germainux.com/main/business-process-workflow-monitoring.md) ### Correlation The ability to connect and relate multiple entities within GermainUX, such as: | From ↔ To | Details | | - | - | | Datasources ↔ KPIs | • Maps raw events, logs, metrics, and traces to normalized business or technical indicators. • Preserves lineage from source telemetry to calculated KPI values and thresholds. | | KPIs ↔ Portlets | • Associates each visual component with the KPIs, filters, time windows, and aggregations it displays. • Enables contextual drilldown from summary visualization to underlying signals. | | Portlets ↔ Dashboards | • Groups related portlets into role-specific analytical workspaces. • Supports business, operational, and technical views over the same correlated data model. | | Events ↔ Business outcomes | • Links technical events and user behavior to conversion, revenue, SLA, or process outcomes. • Quantifies impact so incidents can be prioritized by business consequence. | Correlation is key to **root-cause analysis (RCA)**, allowing users to understand *why* an issue occurs, not just *what* happened. More details on [Correlation.](https://docs.germainux.com/main/correlation-and-tracing.md) ### Dashboard A configurable workspace composed of multiple portlets that provides a consolidated view of performance, insights, and alerts. Dashboards can be tailored for: | Audience | Example | | - | - | | Business (e.g., conversion, revenue) | • Executive dashboard tracking conversion rate, revenue-at-risk, abandonment, and campaign impact. | | Operations (e.g., process efficiency) | • Operations dashboard showing workflow throughput, SLA status, queue delays, and exception volume. | | Technology (e.g., performance, errors) | • Engineering dashboard monitoring latency, availability, error rate, API health, and infrastructure saturation. | They serve as the **primary entry point for analysis and decision-making**. More details on [Dashboard](https://docs.germainux.com/main/dashboard-visibility-team-owners.md). ### Datasource Any system or technology from which GermainUX collects data, including: | Source | Examples | | - | - | | Applications (e.g., CRM, eCommerce) | • Salesforce, ServiceNow, SAP, Oracle, Shopify, custom web applications, and internal portals. | | Servers and infrastructure | • Linux/Windows hosts, Kubernetes clusters, cloud services, network devices, queues, and schedul | Datasources enable GermainUX to provide **end-to-end visibility across business and technology layers**. More details on [Datasource](https://docs.germainux.com/main/data-source.md). ### KPI (Key Performance Indicator) A measurable indicator used to evaluate performance across business, UX, process, or technical dimensions. Examples: | KPI | Details | | - | - | | Conversion rate | Percentage of eligible users or transactions that complete the target business outcome. | | Drop-off rate | Percentage of users or transactions that abandon a workflow before completion. | | Page latency | Measured response and rendering time for pages, views, or key interactions. | | Error rate | Frequency of application, API, browser, or transaction failures within a defined time window. | KPIs are the foundation for **monitoring, alerting, and optimization**. More details on [KPIs](https://docs.germainux.com/main/kpis.md). ### Portlet A visual component within a dashboard that displays one or more KPIs. Portlets: | Insight | Details | | - | - | | Where users succeed | • Surfaces the steps, entry points, and behaviors most commonly associated with successful completion. • Supports replication of effective patterns across journeys, segments, and channels. | | Where friction occurs | • Detects steps with repeated clicks, slow responses, validation loops, errors, | 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: | Outcome | Details | | - | - | | Conversion (success) | • Identifies the dominant na | 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: | Use | Details | | - | - | | Generate insights | • Transforms telemetry, KPI trends, and correlated evidence into concise analytical summaries. • Highlights anomalies, patterns, risks | 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](https://docs.germainux.com/main/ai-settings.md). ### AI Recommendations Automatically generated guidance based on analyzed data, sessions, and patterns. They provide: | Output | Details | | - | - | | Prioritized issues | • Ranks detected problems by severity, user impact, business value, recurrence, and SLA exposure. • Groups related symptoms to reduce noise and accelerate triage. | | Suggested actions | • Provides recommended remediation, investigation, escalation, or optimization steps based on observed evidence. • Can link to automation workflows, runbooks, tickets, or accountable teams. | | Estimated impact (e.g., revenue loss or gain) | • Estimates potential revenue, conversion, productivity, or customer-experience impact using correlated business metrics. • Supports prioritization by quantifying expected benefit or risk reduction. | AI Recommendations help teams move from **data → decision → action faster**. More details on [AI-driven Insights & Recommendations](https://docs.germainux.com/main/ai-driven-insights.md) ### Evidence (Session, Logs, Traces) Direct, verifiable data supporting an insight or issue, including: | Type | Details | | - | - | | Session replay | • Provides visual playback of user interactions, navigation, inputs, and observed behavior. • Links UX symptoms to the exac | 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: | Capability | Details | | - | - | | Visualize user experience | • Replays clicks, navigation, scrolling, form interactions, browser context, and page behavior. • Shows the sequence of actions that preceded success, abandonment, or failure. | | Identify friction points | • Detects rage clicks, dead clicks, repeated attempts, hesitation, errors, and confusing interaction patterns. • Correlates friction with latency, device type, browser, geography, and user segment. | | Validate issues | • Confirms whether alerts, reports, or AI recommendations reflect real user impact. • Provides evidence for debugging, prioritization, stakeholder communication, and remediation. | GermainUX enhances session replay with **automated insights extraction**. More details on [Real User Monitoring/Recording & Session Replay](https://docs.germainux.com/main/user-monitoring-and-replay.md). ### Alert A real-time notification triggered when: | Trigger | Details | | - | - | | A KPI crosses a threshold | • Fires when a metric exceeds configured static, dynamic, or SLA-based limits. • Supports severity, scope, affected segment, and time-window conditions. | | An anomaly is detected | • Triggers on statistically unusual patterns, deviations from baseline, or abnormal trend changes. • Reduces false positives by evaluating context, seasonality, recurrence, and correlated signals. | | A business-critical issue occurs | • Notifies teams when failures affect revenue, conversion, compliance, SLA, or priority workflows. • Escalates based on business impact and configured ownership rules. | Alerts can include: | Content | Details | | - | - | | Context | • Includes affected KPI, datasource, application, workflow, user segment, time window, and severity. • Clarifies what changed, where it occurred, and who or what is impacted. | | Evidence | • Attaches supporting logs, traces, session replays, events, screenshots, or correlated signals. • Provides verifiable data for triage and root-cause analysis. | | Recommended actions | • Suggests next steps such as investigation, escalation, rollback, workflow execution, or automated remediation. • Can reference runbooks, rules, owners, or automation actions. | They enable **proactive issue detection and response**. More details on [Alert](https://docs.germainux.com/main/alert-email-and-sms.md). ### Rule A configurable logic layer that defines how GermainUX: | Function | Details | | - | - | | Detects issues | • Evaluates conditions, thresholds, patterns, and correlations across monitored data streams. • Identifies exceptions, degradations, anomalies, and business-process failures. | | Generates insights | • Transforms rule matches into contextual findings with severity, scope, and supporting evidence. • Enables consistent classification of incidents, risks, and optimization opportunities. | | Executes actions | • Triggers notifications, tickets, workflows, scripts, API calls, or remediation actions when criteria are met. • Applies governance through schedules, ownership, permissions, and escalation logic. | Rules can power: | Use Case | Details | | - | - | | Alerts | • Defines alert criteria, severity, suppression, routing, escalation, and notification logic. • Ensures alerts are generated only when meaningful conditions are satisfied. | | Automations | • Determines when remediation, workflow, data update, or system action should run. • Controls execution using conditions, dependencies, schedules, and approval requirements. | | AI-driven behaviors | • Guides prompt execution, recommendation generation, summarization, and agentic actions. • Applies guardrails so AI outputs remain contextual, auditable, and policy-aligned. | More details on rules for [analytics](https://docs.germainux.com/main/rules-advanced-automated-analytics.md) and for [automation](https://docs.germainux.com/main/rules.md). ### SLA (Service-Level Agreement) Defines expected performance thresholds (e.g., uptime, latency, response time). GermainUX monitors SLA compliance and: | Capability | Details | | - | - | | Detects breaches | • Compares observed performance, availability, and response metrics against configured SLA targets. • Identifies actual and projected violations by service, workflow, customer, or priority level. | | Triggers alerts | • Notifies owners when SLA risk, degradation, or breach conditions are detected. • Routes alerts by severity, service ownership, business impact, and escalation policy. | | Supports remediation | • Links breaches to evidence, root-cause signals, runbooks, and recommended actions. • Can initiate workflows or automation to restore service before impact expands. | More details on [SLAs](https://docs.germainux.com/main/slas.md). ### Report A structured output (PDF, CSV, HTML) summarizing: | Section | Details | | - | - | | KPIs | • Summarizes measured performance, trends, targets, variances, and threshold status. • Provides period-over-period comparison for business, UX, operational, and technical metrics. | | Insights | • Highlights notable patterns, anomalies, correlations, and root-cause findings. • Explains what changed, why it matters, and which entities are affected. | | Recommendations | • Lists suggested actions, owners, priorities, and expected impact. • Connects recommendations to supporting evidence and remediation options. | | Evidence | • Includes session replays, logs, traces, events, screenshots, and related artifacts. • Supports auditability, stakeholder review, and operational follow-up. | Reports can be scheduled or generated on demand to support **stakeholder communication and decision-making**. More details on [Report](https://docs.germainux.com/main/reporting-automatic.md). ### Template Defines how alerts, reports, or dashboards are formatted and presented. Templates ensure: | Benefit | Details | | - | - | | Consistency | • Standardizes layout, terminology, branding, sections, and delivery format across outputs. • Reduces variation in how alerts, dashboards, and reports communicate operational information. | | Customization | • Allows content, fields, filters, audience, thresholds, and formatting to be adapted by use case. • Supports role-specific views for executives, operations, engineering, and support teams. | | Scalability across teams and use cases | • Enables reusable definitions that can be applied across applications, workflows, environments, and customers. • Simplifies rollout, maintenance, and governance of standardized GermainUX configurations. | More details on [Template](https://docs.germainux.com/main/edit-a-template.md). ### Workspace The GermainUX user interface where users: | Activity | Details | | - | - | | Monitor performance | • Provides real-time visibility into KPIs, dashboards, alerts, service health, and business-process status. • Supports monitoring across applications, infrastructure, users, workflows, and data sources. | | Explore insights | • Enables investigation of anomalies, recommendations, evidence, correlations, and root-cause findings. • Supports drilldown from summary views to sessions, logs, traces, journeys, and related entities. | | Configure dashboards | • Allows users to assemble portlets, filters, layouts, KPIs, and audience-specific analytical views. • Supports operational, technical, business, and executive workspace configuration. | | Trigger actions | • Provides controlled execution of notifications, workflows, automations, tickets, and remediation actions. • Connects analysis and diagnosis to operational response within the same interface. | It is designed to support: \ 👉 **Analysis (What is happening?)** \ 👉 **Diagnosis (Why is it happening?)** \ 👉 **Action (What should we do?)** More details on [Workspace](https://docs.germainux.com/main/workspace.md). ## Next * Review the types of real-time [Insights](https://docs.germainux.com/main/insights-to-boost-ux.md) you can get with GermainUX * Review GermainUX’s [preconfigured integrations and capabilities](https://docs.germainux.com/main/monitoring.md) across supported applications, frameworks, databases, operating systems, infrastructure, and enterprise technologies. * Check the other real-time [automation](https://docs.germainux.com/main/automation.md) (alerting, predicting, reporting, resolving, etc.) you can enable with GermainUX * And last but not least, check our [Compliance and Security](https://docs.germainux.com/main/compliance-privacy-and-security.md) program. ## Get Help > **[Contact GermainUX Support](https://docs.germainux.com/main/support.md)** > > 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. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.