A TLA+ model checker compiled to WebAssembly
A library to create a trace of your node app per Google's Trace Event format.
OpenTelemetry Tracing
Get v8 stack traces as an array of CallSite objects.
Trace the original position through a source map
OpenTelemetry Node SDK provides automatic telemetry (tracing, metrics, etc) for Node.js applications
Write state machines once in TypeScript. The compiler mathematically proves correctness via TLA+, then generates runtime code and Postgres constraints from the same source.
Datadog APM tracing client for JavaScript
OpenTelemetry Jaeger propagator provides HTTP header propagation for systems that are using Jaeger HTTP header format.
An extendable Error class that actually works, with TypeScript definition files, supporting old and new style classes and compatibility even with the oldest browsers
OpenTelemetry Collector Trace Exporter allows user to send collected traces to the OpenTelemetry Collector
Minimal lightweight logging for JavaScript, adding reliable log level methods to any available console.log methods
OpenTelemetry Web Tracer
OpenTelemetry Collector Exporter allows user to send collected traces to the OpenTelemetry Collector
OpenTelemetry Collector Exporter allows user to send collected traces to the OpenTelemetry Collector using protobuf over HTTP
Chrome Trace Events interfaces
Node.js binding for libdatadog
Analyze the output of tsc --generatetrace
Error.captureStackTrace ponyfill
OpenTelemetry instrumentation for `knex` database SQL query builder
OpenTelemetry AWS Xray propagator provides context propagation for systems that are using AWS X-Ray format.
Lambda client library that supports hybrid tracing in node js
OpenTelemetry Zipkin Exporter allows the user to send collected traces to Zipkin.
OpenTelemetry Google Cloud Trace Exporter allows the user to send collected traces to Google Cloud Trace.
A command line filter utility for processing [[http://research.microsoft.com/en-us/um/people/lamport/tla/tools.html][TLA+ Tools]] output resulting created when model checking [[[http://research.microsoft.com/en-us/um/people/lamport/tla/book.html][TLA+ language]]] formal model generated using [[https://github.com/jarjuk/tla-sbuilder][sbuilder]] -tool.
A set of [mustache] templates extending [tla-trace-filter] -tool to create a self extracting achieve for API traces generated, when model checking formal models created by [tla-Sbuilder] -tool. Also includes Ruby classes to extract test cases from archive extract. Use case: Formal models, built using [tla-sbuilder], and model checked using [TLA+tools]], can generate /API Traces/, which represent end-to-end scenarios executing across system services in the formal model. An API Trace is composed of steps, with each step giving 1) a (formal) system state before the API call, 2) the API call exercised together with (formal model) value bindings of request parameters, 3) API response returned, and 4) the (formal) system state after the API call. A API Trace can be mapped to /Unit Tests/ on implementation with each Unit Test corresponding a step in the API Trace. After executing each of the individual Unit Tests, the aggregate result can be interpreted as an execution of a "virtual" System Test - considerably easier than managing the execution a System Test as a single unit. The purpose of =tla-trace-arch= GEM is create a self extracting archive, which can be safely distributed to system service developers for extracting API Trace Steps to create unit tests for the service being developed by the developer. Ref: - https://github.com/jarjuk/tla-trace-filter - https://mustache.github.io/mustache.5.html - https://github.com/jarjuk/tla-sbuilder - http://research.microsoft.com/en-us/um/people/lamport/tla/tools.html