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

# GlassFish Server Monitoring

> Catch SEVERE errors in your GlassFish server logs as they happen, and see which instances and applications they hit.

Components
[`Engine`](https://docs.germainux.com/deploy/germain-ux-engine)
[`JS Profiler`](https://docs.germainux.com/deploy/germain-ux-js-profiler)
[`RPA Bot Recorder`](https://docs.germainux.com/deploy/germain-ux-rpa-bot-recorder)
[`RUM JS`](https://docs.germainux.com/deploy/germain-ux-rum-js)
[`RUM Extension`](https://docs.germainux.com/deploy/germain-ux-rum-extension)

Availability
8.6.9 or later

> [card] [What Is Monitored](#what-is-monitored)
>
> SEVERE log entries

> [card] [How It Works](#how-it-works)
>
> Log monitor and parser

> [card] [Deploy](#deploy)
>
> Two wizards on one Engine

> [card] [KPIs](#kpis)
>
> Glassfish Events

## Overview

GermainUX reads the `server.log` of each GlassFish instance and turns every `SEVERE` entry into an event you can count, group and alert on. A connection pool that runs dry, a failed deployment or an `OutOfMemoryError` shows up as a spike of events on the instance where it happened, with the full message. [Error categorization](https://docs.germainux.com/analytics/data-categorization.md) groups repeated messages, so a new error stands out from the known ones. Your team learns about server-side failures without opening log files on each instance.

> [card] SEVERE Errors as Events
>
> Each `SEVERE` entry becomes a **Glassfish Events** event, with the complete message, including stack traces.

> [card] Spikes per Instance
>
> See which instance produces the errors, and when the count jumps above its normal level.

> [card] New Errors Stand Out
>
> Similar messages are grouped, so you can tell a new problem from one you already know.

> [card] Alerts on What Matters
>
> Add an SLA on the event count, and get an alert when errors rise on an instance.

### Questions It Answers

* Which GlassFish instances are logging SEVERE errors right now?
* Did errors increase after the last deployment?
* Which error messages are new today?
* How often does a known error, such as a connection pool timeout, come back?
* Is every instance still writing a server log that GermainUX receives?

## What Is Monitored

| Area | What GermainUX monitors |
| - | - |
| **Server log errors** | Every `SEVERE` entry in `server.log`, with its timestamp and complete message, including multi-line stack traces |
| **Availability** | Up/down status and response time of the applications GlassFish serves, checked on a schedule with [synthetic HTTP checks](https://docs.germainux.com/automation/synthetic-http-execution.md) |
| **Host** | CPU, memory, disk and network of the GlassFish server, and whether the Java process is running. See [Linux monitoring](https://docs.germainux.com/integrations/linux-redhat-suse-monitoring.md) or [Windows monitoring](https://docs.germainux.com/integrations/windows-monitoring.md). |
| **User experience** | Real-user page performance, JavaScript errors and Session Replay for the web applications GlassFish hosts, with [RUM JS](https://docs.germainux.com/deploy/germain-ux-rum-js.md) or the [RUM Extension](https://docs.germainux.com/deploy/germain-ux-rum-extension.md) |

## Analytics, Alerts and Automation

### AI Analysis

Ask [AI Explore](https://docs.germainux.com/analytics/ai-driven-insights.md) questions such as "Which GlassFish errors increased this week?" and get the answer without building a report. [Outlier detection](https://docs.germainux.com/analytics/outlier-detection.md) flags unusual spikes in the error count.

### Dashboards and Reports

GermainUX ships the **GlassFish Overview** dashboard as a starting point. In the left menu, go to **Dashboards > All**, and then open **GlassFish Overview** in the **GlassFish** folder. It shows the number of `SEVERE` events per day in three charts: **Server Events**, **Server Events by Instance** and **Server Events by Application**. Click a chart to open the **Glassfish Events** KPI behind it.

![GlassFish Overview dashboard showing SEVERE events per day in total, by instance and by application, with the previous week as a dashed line](https://mintcdn.com/germain-ux/f8yIBlQJJNs9EW1v/images/main/glassfish-monitoring/glassfish-overview-dashboard.png?fit=max\&auto=format\&n=f8yIBlQJJNs9EW1v\&q=85\&s=1cdb975c910084155fd50fe339615b8a)

GlassFish Overview Dashboard - GermainUX

Build your own [dashboards and reports](https://docs.germainux.com/dashboards/dashboard-and-report.md) on the **Glassfish Events** KPI: errors by instance, error trends over time, and the most frequent messages.

### SLAs and Alerts

**Glassfish Events** has no default SLA. Add an [SLA](https://docs.germainux.com/analytics/slas.md) on the event count per instance, and get an [alert](https://docs.germainux.com/automation/notifications.md) by email, SMS, Slack or Teams when errors rise.

### Automation

When an SLA is breached, an [automated action](https://docs.germainux.com/automation/automated-actions.md) can run a diagnostic script, call an HTTP endpoint or open an incident.

## How It Works

server.log
Log Directory Monitor
Server Log Parser
Glassfish Events
Alerts

You deploy two components to the GermainUX Engine that can read the GlassFish log directory:

| Component | What it does |
| - | - |
| **Glassfish Log Directory Monitor** | Watches the log directory and sends new entries of the file named `server.log` to the server log parser |
| **Glassfish Server Log Parser** | Reads each log entry, including multi-line messages, and stores every `SEVERE` entry as a **Glassfish Events** event |

The Engine reads the log files directly, so it runs on the GlassFish host or on a server that can read the log directory. See [File and Log Monitoring](https://docs.germainux.com/integrations/file-log-monitoring.md) for how GermainUX reads log files.

## Before You Start

* A GermainUX Engine is deployed on the GlassFish host, or on a server that can read its log directory. See [GermainUX Engine](https://docs.germainux.com/deploy/germain-ux-engine.md).
* The Engine's account can read the instance's log directory, for example `glassfish/domains/domain1/logs`.
* GlassFish writes `server.log` in its default format, where each entry starts with bracketed fields such as `[2026-11-12T10:15:30.123+0000] [glassfish 7.0] [SEVERE]`.

A `SEVERE` entry in that format looks like this:

```text theme={null}
[2026-11-12T10:15:30.123+0000] [glassfish 7.0] [SEVERE] [RAR5117] [javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.ConnectionManagerImpl] [tid: _ThreadID=87 _ThreadName=http-listener-1(4)] [timeMillis: 1794564930123] [levelValue: 1000] [[
  RAR5117 : Failed to obtain/create connection from connection pool [ ordersPool ]. Reason : com.sun.appserv.connectors.internal.api.PoolingException: In-use connections equal max-pool-size and expired max-wait-time.]]
```

## Deploy

**1. Deploy the server log parser**

In the left menu, go to **Settings > Wizards**. On the **Parser Deployment** card, click **Add**, and fill in the fields:

| Field | Value |
| - | - |
| **Component Type** | `Glassfish Server Log Parser` |
| **Monitored Application** | The application the GlassFish data belongs to |
| **Monitor Name** | A name you recognize, for example `Glassfish Server Log Parser - gf-app-01` |
| **Monitoring Node** | The Monitoring Node and Engine that can read the GlassFish log directory |

Finish the wizard.

![Parser Deployment wizard with Glassfish Server Log Parser selected as the Component Type](https://mintcdn.com/germain-ux/f8yIBlQJJNs9EW1v/images/main/glassfish-monitoring/parser-deployment-glassfish-server-log-parser.png?fit=max\&auto=format\&n=f8yIBlQJJNs9EW1v\&q=85\&s=d5b35d2e5219704135d23be691b2eeef)

Parser Deployment Wizard with the Glassfish Server Log Parser - GermainUX

**2. Deploy the log directory monitor**

On the **Directory Monitor Deployment** card, click **Add**, and fill in the fields:

| Field | Value |
| - | - |
| **Component Type** | `Glassfish Log Directory Monitor` |
| **Directory** | The instance's log directory, for example `/opt/glassfish7/glassfish/domains/domain1/logs` |
| **Monitor Name** | For example `Glassfish Log Directory Monitor - gf-app-01` |
| **Monitoring Node** | The same Monitoring Node and Engine as the parser |

Finish the wizard. GermainUX starts reading `server.log`.

![Directory Monitor Deployment wizard with Glassfish Log Directory Monitor selected as the Component Type](https://mintcdn.com/germain-ux/f8yIBlQJJNs9EW1v/images/main/glassfish-monitoring/directory-monitor-deployment-glassfish.png?fit=max\&auto=format\&n=f8yIBlQJJNs9EW1v\&q=85\&s=76b28fb68a9c696bcfa181153ab64049)

Directory Monitor Deployment Wizard for GlassFish Logs - GermainUX

Repeat both steps for each GlassFish instance.

## Validate

**1. Find a recent SEVERE entry**

On the GlassFish host, check that `server.log` gets new `SEVERE` entries:

```bash theme={null}
grep -c "\[SEVERE\]" /opt/glassfish7/glassfish/domains/domain1/logs/server.log
```

**2. Find the events in GermainUX**

After the next `SEVERE` entry is written, open the **Glassfish Events** KPI in GermainUX Workspace. Check that the event shows the instance and the complete message.

![Analysis of the Glassfish Events KPI with the event count, the daily trend and the events by application and by instance](https://mintcdn.com/germain-ux/f8yIBlQJJNs9EW1v/images/main/glassfish-monitoring/glassfish-events-analysis.png?fit=max\&auto=format\&n=f8yIBlQJJNs9EW1v\&q=85\&s=3bdebf9c0bc51cbae1af3437cca84ae5)

Glassfish Events Analysis - GermainUX

## Troubleshooting

> [accordion] No GlassFish events appear
>
> Check that both components run on the same Engine, that the Engine's account can read the log directory, and that the log file is named `server.log`. Then check that `server.log` has `SEVERE` entries since the components were deployed. Entries at other levels, such as `WARNING` or `INFO`, don't create events.

> [accordion] Entries are not parsed
>
> GermainUX expects GlassFish's default log format, with bracketed fields at the start of each entry. If the logging configuration switched `server.log` to another formatter, switch it back to the default for the monitored instance.

## Security and Privacy

GlassFish monitoring data includes personal data:

* **Free text**: the message of each `SEVERE` entry, including stack traces. It contains whatever GlassFish and the deployed applications write into it, such as user names, request data or connection details, so treat it as possibly containing personal or customer data.

To mask, anonymize or exclude this data, see [Data Privacy](https://docs.germainux.com/management/compliance-privacy-and-security/data-privacy.md).

## KPIs

| KPI | What it holds | Data model |
| - | - | - |
| **Glassfish Events** | One event per `SEVERE` entry in `server.log`, with the complete message | `GenericEvent` |

**Glassfish Events** has no default SLA. Add the thresholds you need. See [KPIs](https://docs.germainux.com/analytics/kpis.md) and [SLAs](https://docs.germainux.com/analytics/slas.md).

## Related Documentation

> [card] [Java Monitoring](https://docs.germainux.com/integrations/java-monitoring.md)
>
> Code-level monitoring of Java applications

> [card] [File and Log Monitoring](https://docs.germainux.com/integrations/file-log-monitoring.md)
>
> How GermainUX reads log files

> [card] [Automation](https://docs.germainux.com/automation.md)
>
> More Automation Features

## Get Help

The GermainUX team can help you monitor GlassFish instances that use a custom log format, or collect more log levels.

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