Skip to main content
Availability8.6.9 or later

What Is Monitored

SEVERE log entries

How It Works

Log monitor and parser

Deploy

Two wizards on one Engine

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

SEVERE Errors as Events

Each SEVERE entry becomes a Glassfish Events event, with the complete message, including stack traces.

Spikes per Instance

See which instance produces the errors, and when the count jumps above its normal level.

New Errors Stand Out

Similar messages are grouped, so you can tell a new problem from one you already know.

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

Analytics, Alerts and Automation

AI Analysis

Ask AI Explore questions such as “Which GlassFish errors increased this week?” and get the answer without building a report. Outlier detection 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

GlassFish Overview Dashboard - GermainUX

Build your own dashboards and reports 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 on the event count per instance, and get an alert by email, SMS, Slack or Teams when errors rise.

Automation

When an SLA is breached, an automated action can run a diagnostic script, call an HTTP endpoint or open an incident.

How It Works

server.logLog Directory MonitorServer Log ParserGlassfish EventsAlerts
You deploy two components to the GermainUX Engine that can read the GlassFish log directory: 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 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.
  • 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:

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:Finish the wizard.
Parser Deployment wizard with Glassfish Server Log Parser selected as the Component Type

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:Finish the wizard. GermainUX starts reading server.log.
Directory Monitor Deployment wizard with Glassfish Log Directory Monitor selected as the Component Type

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

Glassfish Events Analysis - GermainUX

Troubleshooting

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

KPIs

Glassfish Events has no default SLA. Add the thresholds you need. See KPIs and SLAs.

Java Monitoring

Code-level monitoring of Java applications

File and Log Monitoring

How GermainUX reads log files

Automation

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.

Contact GermainUX Support

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.

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.