Instrumentation

As explained in Functional Programming in JavaScript

The process of inserting tracking code into software so execution behavior can be observed or measured.

<script src="imperative-show-student-program.js" data-cover></script>

How Functional Programming in JavaScript covers it

How deep it goes

Explains a three-phase workflow and tracker-line mechanism, but defers detailed setup to an appendix.

Examples

Uses Blanket.js, QUnit, script attributes, and imperative and functional showStudent tests.

What it assumes

Assumes existing JavaScript unit tests and introduces coverage instrumentation as their measurement complement.

What you can do after

Apply it via Blanket.js to collect and display JavaScript statement-coverage results.

How it connects

Connects instrumentation with code coverage, unit testing, statement coverage, and test runners.

liveBookmanning.com

Read Functional Programming in JavaScript on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Cloud Observability in ActionInstrumentation is the practice of adding software mechanisms that emit telemetry about a system’s behavior and state.
• 

  liveBookmanning.com
  Modern CInstrumentation is the insertion of measurement-related operations into a program or execution environment.
• 

  liveBookmanning.com
  Effective Platform EngineeringInstrumentation is the addition of code or integration components that emit telemetry from software during execution.
• 

  liveBookmanning.com
  Modern C, Third EditionInstrumentation is the addition of code or mechanisms that observe or record properties of program execution.
• 

  liveBookmanning.com
  Troubleshooting Java, Second EditionInstrumentation is the insertion or activation of runtime measurement code to record program execution behavior.
• 

  liveBookmanning.com
  Natural Language Processing in Action, Second EditionModel instrumentation is the addition of observations or logging that exposes a model's internal computations during execution.
• 

  liveBookmanning.com
  Logs and TelemetryInstrumentation is the insertion or provision of code that records execution behavior and emits telemetry.
• 

  liveBookmanning.com
  Google Anthos in ActionInstrumentation is the inclusion of code or integrations that emit measurements and diagnostic signals about software execution.
• 

  liveBookmanning.com
  Secure APIsInstrumentation is the practice of preparing software to emit telemetry and collecting that telemetry for analysis.
• 

  liveBookmanning.com
  Code Like a Pro in Rusttracing is a Rust library for instrumenting programs and emitting structured diagnostic telemetry.
• 

  liveBookmanning.com
  Fast Python: High performance techniques for large datasets
• 

  liveBookmanning.com
  Effective Conversational AIInstrumentation is the deliberate collection and storage of operational data points from a software interaction for later analysis or processing.

Compare how 13 books explain instrumentation →

Related concepts

• telemetryproduces · Telemetry is automatically generated or collected operational data describing a system’s activity, state, behavior, or performance.
• OpenTelemetryuses · OpenTelemetry is an open, vendor-neutral observability standard and framework for instrumenting software and generating, collecting, and exporting telemetry such as traces, metrics, and logs.
• trajectoryproduces · A trajectory is an ordered sequence of states, actions, events, or operations that records or describes progression through successive steps or over time.
• monitoringproduces · Monitoring is the ongoing observation and measurement of a system’s behavior, state, or operational signals to assess its condition and detect changes or problems.
• signalproduces · A signal is an observable value, event, or pattern that conveys information about a condition, state, or phenomenon.
• Prometheus client libraryused by · A Prometheus client library is a language-specific library for defining, collecting, and exposing application metrics in a format Prometheus can collect.

This explainer was generated by Manning's knowledge graph from the text of Functional Programming in JavaScript. The section links point to the parts of the book it draws on.