Analysis updated 2026-07-09 · repo last pushed 2014-04-25
Monitor JBoss memory usage on OpenShift to catch issues before they cause downtime.
Collect and publish scheduled server health metrics to an external monitoring system.
Enable or disable specific metrics groups for a custom JBoss monitoring setup.
| ncdc/jboss-openshift-metrics-module | hyperionelectronicsco/jarvis | asutosh936/job-finder-app | |
|---|---|---|---|
| Stars | 1 | 1 | 0 |
| Language | Java | Java | Java |
| Last pushed | 2014-04-25 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | hard | moderate | moderate |
| Complexity | 4/5 | 2/5 | 2/5 |
| Audience | ops devops | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires building with Maven, manually copying files into the JBoss modules directory, editing standalone config, and setting up Quartz as a separate JBoss module.
The jboss-openshift-metrics-module is a plugin for JBoss application servers that periodically collects performance and health metrics (like memory usage) and publishes them externally. It's designed for teams running Java applications on the OpenShift platform who need visibility into what their server is doing under the hood. At a high level, it works by reading internal server statistics on a schedule you define, for example, every five seconds. You configure it by specifying which metrics to gather (such as heap memory used or maximum memory available) and giving each one a label that gets sent along with the data when it's published. You can also individually enable or disable specific metrics, groups of metrics, or data sources as needed. This would appeal to operations engineers, DevOps teams, or anyone responsible for keeping a JBoss-based Java application running smoothly in an OpenShift environment. For instance, if you're running a customer-facing web app and want to monitor whether memory usage is creeping toward a critical threshold, this module grabs those numbers on a schedule and ships them out so your monitoring system can alert you before things break. Installing it requires building the project with Maven, manually copying files into the JBoss modules directory, and editing the server's standalone configuration file to activate the extension. It also depends on having the Quartz scheduling library set up as a separate JBoss module. This manual setup means it's really intended for people already comfortable administering JBoss servers, it's not a plug-and-play tool but rather a building block for custom monitoring setups.
A JBoss plugin that collects server performance metrics like memory usage on a schedule and publishes them for external monitoring, designed for Java apps running on OpenShift.
Mainly Java. The stack also includes Java, JBoss, Maven.
Dormant — no commits in 2+ years (last push 2014-04-25).
No license information is provided in the repository, so usage terms are unclear.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.