One of the things we're building at OmniFish - a new monitoring console! #25758
Replies: 2 comments 1 reply
-
|
And yes, we know that there are already great tools to capture metrics, logs, etc and then visualise them and process them centrally. This monitoring console is just the beginning. We’re also working on adding support for OpenTelemetry so that the data from GlassFish and your applications can be streamed to more sophisticated tools via the standard protocols. Stay tuned for more news soon! |
Beta Was this translation helpful? Give feedback.
-
|
That looks really interesting. I watched the video and tried to follow it, but for the next one it would be much better if you could add a audio comment to it. Even if its not perfect english it would help me much in following what you showcase. PS: do you know how the stance of glassfish is when to test against LTS releases? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, fellow GlassFish community, we're busy working on new stuff for you and our customers. Besides GlassFish 7.1, which is almost ready to release (it's a matter of days now), and GlassFish 8, which is also almost ready but needs a few more weeks to finish integrating and testing all final versions of components, we have something new to share with you.
We've been working on a new monitoring console that can display monitoring statistics from GlassFish in an easy to follow way and provide insights about what's happening in GlassFish and also trigger alerts and troubleshoot in case of performance degradation of malfunction.
The best thing is that it's a plain WAR app, which can be deployed when needed, and it can even run on any Jakarta EE server and connect to GlassFish instances remotely. Right now, it only supports connecting to a single GlassFish, but we plan to enhance it to connect to multiple installations and get an overview of all of them in the same place.
🧩 The monitoring console is still in its early development stages and not publicly available yet, but here’s a short demo preview:
🎥Screencast_10_29_2025_06:21:01_PM.webm
(The demo has no sound for now.)
The demo shows the monitoring console deployed to GlassFish and showing metrics from the same GlassFish server. Another application is deployed that reads data from database and provides them via a GET HTTP method.
Then, the bombardier tool is used to trigger a continuous stream of 1000 requests for 10 seconds to trigger the GET method, which uses
http-listener-1HTTP thread pool to run requests and theDerbyPoolto connect to the database. As requests are incoming, the number of busy threads climbs to 50, which is the maximum number of threads in the pool, while the number of connections oscillates around 25.This shows that the requests keep the connections busy only about half of the time, and we could actually double the number of threads in the thread pool and still have enough connections to keep them busy.
💬 We’d love your feedback!
What do you think about this?
What would you like that the console displays or features it provides?
Share your thoughts in the comments below.
Ondro Mihalyi
OmniFish director
Beta Was this translation helpful? Give feedback.
All reactions