Monitoring

​

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: 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:

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: When an SLA condition is met, GermainUX can trigger configured automated actions 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: When matching activity is detected again, GermainUX can notify the user. Learn more about Watch & Be Notified.

​

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: A detected failure can trigger additional analysis, notification, or an approved automated action. Learn more about Synthetic Script.

​

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.

​

Monitoring + Automated Action

A monitored condition can trigger one or more configured actions. Depending on the environment and configuration, GermainUX actions can include:

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 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: This closes the automation loop:

​

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

Show all 10

• SyntheticMonitoring
• ScriptExecution
• Integrations
• KPIs, Pivots & Measures

​

Get Help

The content of this document is proprietary to GERMAIN SOFTWARE LLC.