> ## 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. # Monitoring > GermainUX Monitoring continuously observes users, business processes, applications, and technologies to detect conditions that may require attention or action. Components [`Agent`](/main/germainux-agent) [`Engine`](/main/germain-ux-engine) [`JS Profiler`](/main/germain-ux-js-profiler) [`Mobile App`](/main/germain-ux-mobile-app) [`RPA Bot Recorder`](/main/germain-ux-rpa-bot-recorder) [`RUM Extension`](/main/germain-ux-rum-extension) [`RUM JS`](/main/germain-ux-rum-js) [`RUM Windows`](/main/germainux-rum-windows) Availability 2014.1 or later > **[What Can Be Monitored](#what-can-be-monitored)** > > Apps, integrations and components > **[SLA Monitoring](#sla-monitoring)** > > Thresholds and automated responses > **[Validate the Result](#validate-the-result)** > > Confirming actions took effect > **[Security & Control](#security-&-control)** > > Access and data controls ## Overview GermainUX Monitoring continuously observes **users, business processes, applications, and technologies** to detect conditions that may require attention or action. Within Automation, Monitoring provides the **Observe** part of the operational workflow: Observe Analyze Decide Act Validate Monitoring can run continuously, on a schedule, or through synthetic transactions, depending on the monitored system and configured GermainUX components. ## What Can Be Monitored Depending on the application, technology, integration, and deployed GermainUX components, monitoring can include: * User activity, sessions and experience * Errors and exceptions * User friction * Application and page performance * Business processes and workflows * Transactions > **Show all 14** > > * APIs and web services > * Databases and SQL > * Application services > * Logs > * Infrastructure and system metrics > * Integrations > * Availability > * Synthetic user journeys Collected data is converted into GermainUX KPIs, Measures, Pivots, events, transactions, and other monitored facts that can be analyzed and used by Automation. ## Real-Time Monitoring GermainUX can continuously monitor incoming data and evaluate it against configured conditions. For example: **Application Error Detected** \ → Analyze frequency and impact \ → Identify affected users and sessions \ → Create or update a ticket \ → Notify the responsible team \ → Execute an approved action \ → Continue monitoring to validate the resolution Monitoring therefore does not have to stop at detecting an issue. It can initiate the next steps of an automated operational workflow. ## SLA Monitoring SLAs define conditions used to determine whether a monitored KPI is operating within expected limits. SLAs can be configured for conditions such as: * Error volume or rate * Transaction failures * Response time * Availability * Business-process failures * User-experience friction * Infrastructure conditions * Other KPI thresholds When an SLA condition is met, GermainUX can trigger configured [automated actions](/main/automated-actions.md) such as alerts, AI analysis, reports, scripts, API calls, SQL, SSH, WMI, or other authorized actions. ## Watch Specific Activity A **Watch** can be created when a user wants GermainUX to monitor for a specific piece of data or condition. Examples include: * A particular error or exception * A specific user * A failed transaction * A server or application * A Phrase of Interest * Another data condition relevant to an investigation When matching activity is detected again, GermainUX can notify the user. Learn more about [Watch & Be Notified](/main/watch.md). ## Synthetic Monitoring GermainUX can proactively execute recorded user scenarios to validate that critical applications and business processes continue to work as expected. Synthetic monitoring can be used to: * Execute critical user journeys * Validate application availability * Validate transactions * Detect failures before real users report them * Measure transaction performance * Verify critical workflows on a schedule A detected failure can trigger additional analysis, notification, or an approved automated action. Learn more about [Synthetic Script](/main/user-click-synthetic-user-scenario.md). ## Monitoring + AI Analysis Monitoring can automatically initiate **AI Analysis** when a condition requiring investigation is detected. For example: **New Error Detected** \ → Collect occurrences \ → Analyze affected users and sessions \ → AI analyzes available evidence \ → Summarize the issue \ → Recommend next steps \ → Notify the appropriate team This can reduce the amount of manual investigation required before a team begins working on an issue. Learn more about [AI Analysis](/main/ai-driven-insights.md). ## Monitoring + Automated Action A monitored condition can trigger one or more configured actions. Depending on the environment and configuration, GermainUX actions can include: * Send an alert * Notify a user through a Watch * Generate or distribute a report * Perform AI Analysis * Create or update an incident * Call an HTTP endpoint, API, or webhook > **Show all 13** > > * Execute a script > * Execute a local program > * Execute SQL > * Execute an SSH command > * Execute a WMI operation > * Run an RPA or synthetic workflow > * Execute another authorized remediation or operational action [Actions](/main/automated-actions.md) can be **fully automated** or require human review and approval, depending on the organization's requirements. ## Validate the Result Monitoring can continue after an action has been executed. This allows GermainUX to determine whether the monitored condition: * Returned to normal * Continues to occur * Affects additional users or systems * Requires another action * Requires escalation This closes the automation loop: Detect Analyze Act Monitor Validate ## Configure Monitoring The way monitoring is configured depends on what needs to be monitored. GermainUX provides preconfigured monitoring for supported applications, technologies, and integrations. Custom monitoring can also be configured using KPIs, SLAs, Rules, Watches, scripts, synthetic transactions, and other GermainUX capabilities. When a dedicated GermainUX Integration is available, use its deployment and configuration documentation to configure the appropriate monitoring. The Germain Team can also help determine which monitoring and automation capabilities are appropriate for your environment and configure them for you. ## Security & Control Automated monitoring and actions operate according to the permissions, credentials, network access, rules, and GermainUX components configured for the environment. Actions that change data, applications, infrastructure, or customer-facing systems should use appropriate permissions, safeguards, validation, and organizational approval. ## Related Documentation * **Other**[Automation](/main/automation.md) * [Analytics](/main/analytics.md) * [**AI**](/main/ai-driven-insights.md)**Analysis** * [SLAs](/main/slas.md) * [**Rules**](/main/rules.md)**— Advanced Automation** * **Watch &**[**Be Notified**](/main/watch.md) > **Show all 10** > > * [**Synthetic**](/main/user-click-synthetic-user-scenario.md)**Monitoring** > * [**Script**](/main/script.md)**Execution** > * [Integrations](/main/monitoring.md) > * [**KPIs**](/main/user-monitoring-and-replay-kpis.md)**, Pivots & Measures** ## Get Help > **[Contact GermainUX Support](/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.