Projects tagged ‘java’ and ‘monitor’

OpenNMS is the world's first enterprise grade network management platform developed under the open source model. It consists of a community supported open-source project as well as a commercial services, training and support organization.

What is SessionMon?SessionMon is a utility that lets you analyze, test and monitor Servlet sessions at any point in your application's workflow. With this tool, fixing your HTTP session related bugs ... [More] , performance lag, memory over usage, and replication issue are much less painful. Using SessionMon is quick and easy. To get started, all you need to do is download sessionmon.zip file and deploy SessionMon Servlet in your application. Sweet! RequirementsJava Runtime Environment version 1.4 and above Java Servlet Specification 2.3 and above FeaturesUser friendly graphical interface (Access via API also available) Servlet session dump in HTML, XML and JSON format Session ID Number of other active sessions Number of session attributes Latest session attribute update time List of attributes in session Attribute name Attribute object type Non-serializable object indicator Attribute toString value Approximate size (in bytes) of attribute's entire data graph rooted at the object instance Size (in bytes) of attribute in serialized form Total approximate size (in bytes) of all session attributes' entire data graph rooted at the object instance Total size (in bytes) of all session attributes in serialized form Session creation time Session last accessed time Maximum inactive interval in seconds Is new session Session management tester Session replication test in your clustered environment: Analyze replication synchronization and delay. Session invalidation test Future Enhacements Monitoring of session data and replication with E-Mail notification Dump and run tests on all active sessions Getting StartedDownload and save sessionmon.jar into your lib directory along with the dependency JARs that are bundled in the ZIP file. Edit your web.xml to deploy SessionMon Servlet and listeners like this: sessionmon.SessionListener sessionmon.SessionAttributeListener SessionMonServlet sessionmon.SessionMonServlet enabled true server_node_addresses http://localhost:8080,http://localhost:8081 SessionMonServlet /sessionmon/* Navigate to a point/page of your application workflow where you want to monitor session in your favorite web browser. Access SessionMonServlet from the same browser used in previous step. GUI: http://your-host/your-application/sessionmon JSON Dump: http://your-host/your-application/sessionmon?command=dump&type=json XML Dump: http://your-host/your-application/sessionmon?command=dump&type=xml Please refer to the Wiki page on how to access SessionMon via API. ScreenshotsScreenshot #1: Session Dump Screenshot #2: Session Replication Test [Less]

VLMa is a Java application which provides a daemon and a web interface to manage several VLC streamers. It has some nice features like: - dynamic stream assignments (incl. fallback if a server is ... [More] unavailable) - drawing of the servers stats as RRD graphs - and more... It is designed to be used in large networks such as universities or corporate networks. [Less]

Treez is an open source version control monitor and changelog manager with pluggable support for multiple Version Control systems such as Subversion and CVS.

Welcome to the Scene Monitor project. Here you will find various tools to aid in development of 3D applications and games using the open source java 3D scene graph API jMonkey Engine. Scene ... [More] MonitorScene Monitor allows you to visibly explore the structure of your scene graph while your application is running. This makes it a great tool for debugging your application and getting real-time feedback as you tweak various parameters of your scene. More... Whats new in version 1.30?Check out the release notes for details on what's new. Scene WorkerScene Worker lets programmers and designers create, edit and explore objects in the JME scene graph. More... Sub-ProjectsThese projects were developed to fulfill design requirements of Scene Monitor. They are made available for use in other projects under the same licensing terms as Scene Monitor, New BSD. jME JTreeA Swing JTree implementation for a jMonkey Engine scene graph. More... Proprty TableA Swing JTable implementation of a property table. More... [Less]

The main goal of the project is to create a distributed generic system collecting and storing various runtime metrics collections used for system performance, health, quality and availability ... [More] monitoring purposes. The system also provides a set of data-mining algorithms useful for further performance analysis. Allmon is designed to harvest different metrics values coming from many areas of monitoring infrastructure. The collected data are base for quantitative and qualitative performance and availability analysis. Tool collaborates with other analytical tools for OLAP multidimensional analysis and Data Mining processing. The tool can be used for production as well as for development (profiling) and QA (load testing) purposes. To read more go to allmon wiki on main project page. [Less]

The goal of this project is to create a lightweight, system tray based application that will allow for easy, unobtrusive, straightforward, and on demand access to many of Google's wonderfully helpful services.

Easy configurable system to rescan your web applications periodically and send notifications in case of failure. It can send emails or schedule events in your google calendar with sms notification. ... [More] This solution allows your to receive email and sms notifications completely for free. --- Система легко конфигурируется для периодического опроса ваших web-приложений. В случае, если она обнаруживает падение (или просто неожидаемое поведение) web-приложения, она может отослать оповещение в виде электронного письма или нового события в календаре Google (что приведет к получению sms при правильной настройке календаря). Использование GrayGoose позволяет осуществить постоянный мониторинг работоспособности ваших приложений и получать email и sms оповещения абсолютно бесплатно. Важно, что инсталляция GrayGoose, будучи размещенная в дата-центрах компании Google, не зависит от локальных проблем вашей инфраструктуры. [Less]

JmxBuilder Moves to Groovy Release 1.6JmxBuilder has been officially added to Groovy! As of version 1.6 RC1, JmxBuilder has been migrated as part of Groovy Core. While the documentation will remain ... [More] here, all future code release and improvement will be part of Groovy. Download Groovy 1.6 here - http://groovy.codehaus.org/Download You can still download the original JmxBuilder 0.5 beta here. JmxBuilderJmxBuilder is a Groovy-based domain specific language for the Java Management Extension (JMX) API. It uses the builder pattern to create an internal DSL that facilitates the exposure of regular Java and Groovy beans for runtime control and management via the MBean server.The Groovy JMX Builder DSL hides the complexity of creating and exporting management beans via the JMX API and provides a set of natural constructs to interact with the JMX infrastructure. FeaturesDomain Specific Language (DSL) for JMX API using Builder pattern Simplified JMX API's programmability Maintain the natural Groovy syntax Declaratively expose Java/Groovy objects as JMX managed MBeans Support class-embedded or explicit descriptors Inherent support for JMX's event model Seamlessly create JMX event broadcasters Attach event listeners as inline closures Use Groovy's dynamic nature to easily react to JMX events notifications Provides a flexible registration policy for MBean No special interfaces or class path restrictions Shields developer from complexity of JMX API Exposes attribute, constructors, operations, parameters, and notifications Simplifies the creation of connector servers and connector clients Support for exporting JMX timers Getting StartedIt's easy to start using the JmxBuilder DSL (as long as the jar is on your class path). Initialize the builder def jmxBldr = new JmxBuilder()You can optionally provide an MBeanServerConnection that the builder will use during its operations new JmxBuilder(server)Exporting an MBeanLet's say you have Java class called RequestController with the following methods public class RequestController { // constructors public RequestCopntroller() public RequestController(Map resource) // attributes public boolean isStarted() { ... } public int getRequestCount(){ ... } public int getResourceCount() { ... } public void setRequestLimit(int limit){ ... } public int getRequestLimit() { ... } // operations public void start(){ ... } public void stop(){ ... } public void putResource(String name, Object resource){ ... } public void makeRequest(String res) { ... } }You can export an instance of that class for management to an MBeanServer using def ctrl = new RequestController() jmx.export { bean(ctrl) } The code above will export an MBean into the MBeanServer for the specified object instance for management. JmxBuilder will do the following Generate a default JMX ObjectName Export all JMX attributes (in read-only) Export all operations JConsole view of Exported Bean You can see that JmxBuilder exports all attributes, operations, and constructor information automatically using this shorthand notation. You can customize your targeted attributes and operations description that you want to export (see below). Export DescriptorsYou can control, customize, and describe the information that is exported to the MBeanServer. JmxBuilder lets you describe your export information by declaring your descriptors inline or embedding the descriptors inside the object itself Overriding the ObjectNameOne of the thing you can do is to override the object name to customize your export. This is done as followed: jmxBldr.export { bean(target:ctrl, name:"jmx.builder:type=Object") } This willl export the MBean using the object name provided. You can use the string representation or an instance of ObjectName here. See JmxBuilderReference for detail. Controlling Attribute ExportYou can control the description and attribute export using JmxBuilder. Export with Attributes with Wildcard "*"You can use a wildcard character to export all attributes associated with the MBean. The snippet below exports all attributes, however, no operations or constructors will be defined nor exported into the MBeanServer. jmxBldr.export{ bean( target: ctrl, name: "jmx.builder:type=Object", attributes: "*" ) }See JmxBuilderReference for more detail on exporting attributes. Export Attributes by ListThe following code snippet provides a list of attributes to export. Only the listed attributes will be exposed for management. jmxBldr.export{ bean( target: ctrl, name: "jmx.builder:type=Object", attributes: ["Started","RequestCount", "ResourceCount"] ) }This snippet will cause JmxBuilder to export only the attributes listed in key "attributes:" and their associated getter operations. JConsole View See JmxBuilderReference for more detail on exporting attributes. Controlling Operation ExportJmxBuilder lets you describe and export information about operations declared on the underlying bean to be exported as MBean. You can implicitly describe and export all operations (using the wildcard) or specify which operation to export. Export with Operations with Wildcard "*"You can use a wildcard character to export all operations declared on the underlying bean to exported. The snippet below exports all operations, however, no attributes or constructors will be defined nor exported into the MBeanServer. jmxBldr.export{ bean( target: ctrl, name: "jmx.builder:type=Object2", operations: "*" ) }JConsole View You can see that JmxBuilder only exported operations on the MBean (including getter/setters). No attributes were described nor exported. See JmxBuilderReference for more detail on exporting attributes. Export Operations by ListYou can target operations to export by specifying a comma-separated list of the methods on the underlying bean to export for management. jmxBldr.export{ bean( target: ctrl, name: "jmx.builder:type=Object3", operations: ["start","stop", "makeRequest"] ) }JConsole View Notice that only the specified operations are described and export into the MBeanServer. See JmxBuilderReference for more detail on exporting operations. Handling EventsUsing JmxBuilder, you can intercept listen and react to events emitted on the MBeanServer's event bus. Conversely, JmxBuilder lets you emit your own event on the bus to be consumed by registered listeners. Attribute Change EventsOne basic event that JmxBuilder allows you to listen for is "attribute changes". You can set easily set your listener when you setup the bean for export. jmxBldr.export{ bean(target:ctrl, name:"jmx.builder:type=Object", attributes: [ "RequestLimit":[reable:true, writable:true, onChange:{e -> if(e.newValue > 10){ println "***** Warning, high limit detected *****" } } ] ] ) }The closure specified by key "onChange:" will be invoked whenever the attribute "RequestLimit" on the MBean is updated via the setter associated with the attribute. JConsole View Closure Executed Attribute "RequestLimit" updated to 22, causes the onChange event closure to be called. See JmxBuilderReference for more detail on event handling. Operation Call EventsSimilary to attribute change events, JmxBuilder supports callback closures for operation invokation. You can easily set up a listener closure that gets executed whenever an MBean operation is invoked. jmxBldr.export{ bean(target:ctrl, name:"jmx.builder:type=Object", operations: [ "makeRequest":[ onCall:{e -> println "***** A request was made *****" } ] ] ) }In the snippet above, the closure specified by key "onCall:" will be executed after each invokation of opeartion makeRequest on the MBean. Closure Executed See JmxBuilderReference for more detail on event handling. What's NextThe JmxBuilder DSL is capable of much more. Please review the JmxBuilderReference section for a list of all of the capabilities of the tool. FeedbackAll feedbacks are welcome. If you find a bug, don't hesitate to report it. [Less]

Tool to monitor servers