Instrumentation (computer programming): Difference between revisions

Revision as of 23:15, 30 November 2010

Revision as of 04:32, 14 April 2011

Line 1:

In context of [[computer programming]], '''instrumentation''' refers to an ability to monitor or measure the level of a product's performance, to diagnose errors and writingto write trace information. InstrumentationProgrammers isimplement instrumentation in the form of code instructions that monitor specific components in a system (for example, instructions thatmay output logging information to appear on screen). When an application contains instrumentation code, it can be managed using a management tool. Instrumentation is necessary to review the performance of the application. Instrumentation approaches can be of two types, source instrumentation and binary instrumentation.

== Output ==
In programming, instrumentation means the ability of an application to incorporate:

* Code [[Tracing (software)|tracing]] - receiving informative messages about the execution of an application at run time.

* [[Debugging]] and (structured) [[exception handling]] - tracking down and fixing programming errors in an application under development.

* Performance counters - components that allow youthe totracking trackof the performance of the application.

* [[Data logger|Event logs]] - components that allow youthe receivelogging and tracktracking of major events in the execution of the application.

==See also==

* [[Instruction set simulator]] - simulation of all instructions at machine code level to provide instrumentation

* [[Runtime intelligence]] - technologies, managed services and practices for the collection, integration, analysis, and presentation of application usage levels, patterns and practices

* [[Software performance analysis]] - techniques to monitor code performance, including instrumentation

* [[Hardware performance counter]]

==References==