> ## 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.

# Middleware and Integrations

> Monitor message brokers, queues, integration platforms and enterprise services with GermainUX, and trace integration failures to the users and business processes they affect.

Components
[`Engine`](https://docs.germainux.com/deploy/germain-ux-engine)

> [card] [What GermainUX Monitors](#what-germainux-monitors)
>
> Queues, messages, endpoints

> [card] [Supported Technologies](#supported-technologies)
>
> Full list of integrations

> [card] [Automation](#automation-for-integrations)
>
> Act on integration failures

## Overview

Many business transactions depend on middleware and integrations: message brokers, queues, integration platforms, web services and coordination services that connect applications together.

GermainUX monitors these components and correlates their activity with the user actions, application transactions and business processes that rely on them. This helps teams detect stalled queues, failed messages or slow endpoints, and understand which users and workflows are affected.

## What GermainUX Monitors

| Area | Examples |
| - | - |
| Message brokers and queues | Brokers, queues, topics, queue depth, queue time, message age, consumers and producers |
| Streaming | Brokers, topics, partitions, producers, consumers, lag and throughput |
| Integration platforms | APIs, flows, integrations, services, processes and transactions |
| Web services | Endpoint availability, transactions, response time, payload validation and errors |
| Distributed caches and coordination | Member heap, map size and memory, nodes, sessions, connections and latency |

Available metrics depend on the technology, deployment method, accessible interfaces and installed GermainUX components.

![MuleSoft Overview dashboard in GermainUX](https://mintcdn.com/germain-ux/yNXlW51ZNuuaNNHr/images/main/mulesoft-monitoring/mulesoft-overview-dashboard.png?fit=max\&auto=format\&n=yNXlW51ZNuuaNNHr\&q=85\&s=dc60b0926e8d78a9c820defe4505676a)

MuleSoft Overview dashboard - GermainUX

Distributed caches such as Hazelcast get their own overview dashboard.

![Hazelcast Overview dashboard in GermainUX](https://mintcdn.com/germain-ux/eoDC7Ue6Rn5SPFuW/images/main/hazelcast-monitoring/hazelcast-dashboard.png?fit=max\&auto=format\&n=eoDC7Ue6Rn5SPFuW\&q=85\&s=0b8a92e31dbf48a48e74f2e4a18f5158)

Hazelcast Overview dashboard - GermainUX

## Supported Technologies

| Integration | Primary coverage |
| - | - |
| [ActiveMQ](https://docs.germainux.com/integrations/apache-activemq-monitoring.md) | Brokers, queues, topics, messages, consumers, producers, errors, and performance |
| [Apache Kafka](https://docs.germainux.com/integrations/apache-kafka-monitoring.md) | Brokers, topics, partitions, producers, consumers, lag, throughput, and errors |
| [Hazelcast](https://docs.germainux.com/integrations/hazelcast-monitoring.md) | Member heap, map size, map memory, availability, and alerts |
| [IBM WebSphere MQ](https://docs.germainux.com/integrations/websphere-mq-monitoring.md) | Queue depth, queue time, message age, availability, and processing health |
| [MuleSoft](https://docs.germainux.com/integrations/mulesoft-monitoring.md) | APIs, flows, integrations, transactions, errors, availability, and performance |
| [SOAP](https://docs.germainux.com/integrations/soap-monitoring.md) | Endpoint availability, transactions, response time, payload validation, and errors |
| [TIBCO](https://docs.germainux.com/integrations/tibco-monitoring.md) | Services, processes, integrations, transactions, queues, errors, and performance |
| [ZooKeeper](https://docs.germainux.com/integrations/apache-zookeeper-monitoring.md) | Nodes, sessions, connections, availability, latency, and service health |

REST APIs and other HTTP endpoints can also be monitored and called through [HTTP and HTTPS execution](https://docs.germainux.com/automation/synthetic-http-execution.md). Custom data can be sent to GermainUX with the [Data Ingestion API](https://docs.germainux.com/management/data-analysis/data-ingestion-api.md).

## Trace Integration Issues End to End

Integration failures are often invisible to users until a later step fails. With GermainUX you can:

* Correlate messages, service calls and integration transactions with the user action or business process that triggered them. See [Correlation and Tracing](https://docs.germainux.com/analytics/correlation-and-tracing.md).
* Follow a transaction across browser, application, integration and database layers. See [Transaction Insights](https://docs.germainux.com/analytics/transaction-insights.md).
* Detect stalled or failing steps in multi-application business processes. See [Business Process and Workflow Monitoring](https://docs.germainux.com/analytics/business-process-workflow-monitoring.md).
* Prioritize integration errors by the users and workflows they affect. See [Error Analysis](https://docs.germainux.com/analytics/errors-analysis-ai-powered.md).
* Define thresholds for queue depth, lag or response time with [SLAs](https://docs.germainux.com/analytics/slas.md), and detect abnormal changes with [Outlier and Anomaly Detection](https://docs.germainux.com/analytics/outlier-detection.md).

## Automation for Integrations

GermainUX can respond to integration conditions manually, on a schedule or when a configured condition is met.

| Action | Use |
| - | - |
| [HTTP and HTTPS](https://docs.germainux.com/automation/synthetic-http-execution.md) | Call APIs, webhooks, services and integration endpoints |
| [Alerts](https://docs.germainux.com/automation/notifications/alert-email-and-sms.md), [Slack](https://docs.germainux.com/automation/notifications/slack.md) and [Microsoft Teams](https://docs.germainux.com/automation/notifications/microsoft-teams-notification.md) | Notify the responsible team |
| [ServiceNow](https://docs.germainux.com/automation/servicenow.md) and [Moogsoft](https://docs.germainux.com/automation/moogsoft.md) | Create or update incident records |
| [Scripts](https://docs.germainux.com/automation/script.md) and [SQL](https://docs.germainux.com/automation/sql-execution.md) | Run configured diagnostic or recovery procedures |

See [Automation](https://docs.germainux.com/automation.md) for all available actions.

## Deployment

Middleware and integration monitoring is typically collected by the [GermainUX Engine](https://docs.germainux.com/deploy/germain-ux-engine.md). See each technology page above for its specific deployment and configuration steps.

> [!WARNING]
>
> Use least-privilege credentials for monitoring and actions, and follow the organization's security, approval and change-management policies. See [Compliance, Privacy and Security](https://docs.germainux.com/management/compliance-privacy-and-security.md).

## Related Pages

> [card] [Integrations Overview](https://docs.germainux.com/integrations/monitoring.md)
>
> All supported integrations

> [card] [Infrastructure](https://docs.germainux.com/integrations/infrastructure-monitoring.md)
>
> Hosts, containers, cloud and network

> [card] [Transaction Insights](https://docs.germainux.com/analytics/transaction-insights.md)
>
> End-to-end transaction analysis

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/getting-started/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] 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.