Free instrumentation software for windows

MaintainJ, an Eclipse plug-in, generates runtime sequence and class diagrams for a given use case, helping the users to quickly understand a complex Java or J2EE application.
MaintainJ, an Eclipse plug-in, generates sequence and class diagrams for a given use case, helping the users to quickly understand a complex Java or J2EE application.
MaintainJ logs runtime method execution sequence to a file and uses that trace file to render sequence and class diagrams. MaintainJ Instrumentation Wizard instruments a Java/J2EE application and MaintainJ UML Editor renders sequence and class diagram from the trace file.
The following features make MaintainJ a unique and useful tool for Java developers.
a) Generated Diagrams - Runtime sequence and class diagrams for a given use case are generated on demand in a few minutes; no need to prepare and update UML diagrams.
b) Source Untouched - The application code is not changed in anyway; application is rebuilt using AspectJ compiler to capture the method execution sequence at runtime.
c) Collapsible Calls - Method calls in sequence diagram are collapsible. One can easily explore a complex sequence diagram by collapsing and expanding calls as necessary.
d) Focused Diagrams - Only application classes in specified packages are shown in diagrams. All repeat calls occurring in a loop and recursive calls are removed from sequence diagrams.
e) Runtime Diagrams - All classes shown in the diagrams are concrete runtime classes.
f) Eclipse Integration - Double clicking a call or class opens matching method or class in Eclipse.
g) Outline Views - Outline views in both diagrams make navigating a complex diagram easier.
h) Print or Export - Diagrams can be printed or exported as JPEG images.

An inventory, assessment and reporting tool that will find and determine if computers on a network are ready to run Vista The Windows Vista Hardware Assessment is a tool that will find computers on a network and perform a detailed inventory of the computers using Windows Management Instrumentation (WMI).
Through use of the detailed inventory data, the tool will assess and report whether the computers can run Windows Vista, where to find drivers for devices on the computers and provide recommendations for hardware upgrades, where appropriate.
The Windows Vista Hardware Assessment tool does not require the deployment of agent software on the computers being inventoried and assessed. Windows Vista Hardware Assessment will provide a quick, secure and easy way to determine which systems, in a networked environment, are Windows Vista ready.
System requirements:
- Supported Operating Systems: Windows Server 2003 R2 (32-Bit x86); Windows Vista; Windows XP Service Pack 2
- Software Requirements: Microsoft SQL Server 2005 Express Edition for storing inventory and assessment data. Microsoft Word 2003 SP2 or Microsoft Word 2007 and Microsoft Excel 2003 SP2 or Microsoft Excel 2007 for generating reports.
- 1.6-GHz or faster processor minimum
- 1 GB of RAM minimum
- 1 GB of available hard-disk space required
- 10/100 Mbps network adapter required

The Microsoft Management Model Designer (MMD) application was created to be a tool for developing management models The Microsoft Management Model Designer (MMD) application was created to be a tool for developing management models. Management models provide a way to represent all of the areas of manageability for applications and systems services.
You can use the MMD to:
- Build a management framework by defining the managed entities that make up your applications or system services and define how these they relate to each other.
- Import existing instrumentation, such as events and performance counters, into your model.
- Author human-readable knowledge associated with each managed entity, such as event and performance counter descriptions and troubleshooting content.
- Import and export existing MOM 2005 management pack knowledge
- Validate your management model schema.
A health model defines various health states of a system and how that system moves in and out of those health states. It provides a single source for documenting troubleshooting knowledge for an application or service.
A health model describes the following:
- Physical or logical parts of an application or service that an IT Professional (IT Pro) needs to configure, monitor, and report on
- A set of health states the application or service can get into and why
- How to detect and diagnose problems
- How to solve problems
The ultimate goal of creating a health model is to enable the IT Pro to more easily and efficiently maintain systems in a distributed environment. You use the Microsoft Management Model Designer (MMD) to create your health model.
Creating a health model with the Management Model Designer (MMD) includes:
- Building an application structure from predefined components (base classes as defined in the Service Modeling Language Platform) and the relationships between them.
- Building a hierarchy of the logical services and objects the application exposes in a way that is most useful for IT professionals.
- Identifying the functional Aspects for each Managed Entity that are of interest for monitoring.
- Identifying all of the Health States and levels of severity an Aspect can be in.
- Identifying the verification steps that need to be taken to confirm whether an Aspect is in a given Health State.
- Providing the instrumentation that enables the detection of each Health State.
- Identifying the diagnostic steps needed to determine the root cause of the degraded Health State of an Aspect.
- Identifying the recovery steps that need to be taken to resolve a problem and return an Aspect and its parent Managed Entity to full health.
You use the Management Model Designer (MMD) tool to:
- Build a management framework by defining the managed entities that make up your application or system service and define how the entities relate to each other.
- Import existing instrumentation, such as events and performance counters, into your model.
- Enter descriptions and procedures related to Managed Entities for the IT Pro to use for troubleshooting.
- Import and export Operations Manager management pack knowledge.
- Validate your management model.
The Managed Entity framework you create plus the descriptions and procedures you write for each component including Managed Entities, Aspects, Verifiers and Resolvers, become the content for web-based troubleshooting information IT Pros can access through TechNet, as well as output for generating Operations Manager management packs.
System requirements:
- .NET CLR 2.0 and Office Interop Assemblies

NetBeans Profiler, with its tight integration into the NetBeans IDE work flow helps you build reliable and scalable applications With its tight integration into the NetBeans IDE work flow, NetBeans Profiler was designed to enable you to build scalable and reliable software.
Select from several of the most common tasks, such as standard CPU or memory profiling, or simple monitoring. The options are preset to default values by experts. Only the application-specific options are exposed to you. If you need to tune the tools nuts and bolts, switch to custom profiling for full flexibility.
The Profiler can be set up to report only on the methods in which you are interested. Profile the entire application, or a subset, under a realistic workload. Using dynamic bytecode instrumentation and additional algorithms, the NetBeans Profiler obtains runtime information on applications that are too large or complex for other profilers.
Main features:
- Low overhead profiling: you can profile just a subset of the application code - the rest of the code is not instrumented and thus runs at full speed. The profiled subset and the kind of profiling (CPU, memory, etc.) can be changed at any moment during run time.
- CPU Performance profiling: you can profile the entire application, or select a subset of its code to profile based on one or more root methods that you are free to choose. For example, you can set the doGet() method of your servlet as a root, and thus profile only the code of this method and other methods that it calls. The rest of the Java code, including most of the code of your Web/Application server, will run at full speed. Selective profiling based on chosen root methods appears to be a surprisingly good way to reduce the performance overhead and obtain accurate results for heavily multithreaded applications under realistic workload.
- Memory profiling: you can profile only object creation events, which imposes smaller overhead and allows you to detect problems with excessive object allocations. If this is not enough, you can turn on object liveness profiling, that records both object creation and reclamation events. It allows you to see the number, age, allocation paths, and other characteristics of objects currently in memory. It also can help you to detect memory leaks.
- Memory leak debugging: memory leaks are not uncommon with large Java applications. With most of the existing tools, it may take hours to make sure there is really a memory leak, and then to identify leaking objects. Our technology can pinpoint leaking objects for you immediately, based on the special pattern of allocations and reclamations (or lack thereof) that such objects typically demonstrate. You can then check where these objects were allocated, which in many cases is sufficient for identifying the root cause of the leak.
- Task-based profiling: profiling is a complex activity, which may require quite a bit of tuning, and thus learning the tools nuts and bolts. However, our task-based approach makes climbing the learning curve much easier, by first offering you several of the most common tasks, such as standard CPU or memory profiling, or simple monitoring. In these tasks, most of the options are preset to the most common values, and only the most important options are exposed to you. Once you learn more, you can switch to custom profiling, where you can get a full advantage of the flexibility of the advanced NetBeans Profiler technology.
- Threads profiling: you can observe threads & their activity during application execution. The threads profiling offers two views of the threads: "Threads timeline", showing threads activity side-by-side, and "Thread details" showing detailed information about one or more selected threads, including a list of all state changes in the threads life
- Processing collected data offline: you can save snapshots of collected results and process them offline.
System requirements:
- You must have NetBeans IDE installed first. Download it here

The KineticaRT .NET Simulator component provides simulated real-time data. Outputs include sine waves, sawtooth and noise, may be used with very little configuration and can provide reliable waveform test data. It is a member of the KineticaRT family of components, which can be used separately or in unison to build applications for instrumentation, hmi, control, monitoring and test automation.

WMI is an acronym for Windows Management Instrumentation. Mitec WMI Explorer allows software to monitor and control managed resources throughout the network.