Correlation id for node.js
TypeScript definitions for express-correlation-id
Middleware for adding a correlation id to requests being executed, to use with @commercetools/sdk-client
Vizydrop correlation id helper based on async hooks
Correlation id helper based on async local storage
Transparently forward or add correlation id to all requests
Add correlation id to your functions context
Correlation-id handler and Express middleware
Express middleware to set a correlation in Express. The correlation id will be consistent across async calls within the handling of a request.
Correlation id mixin for pino
Express middleware to correlate requests across http calls
Correlation id mixin for pino
Middy middleware to add or forward a correlation id
Structured logging, metrics, correlation ID propagation, and exception handling for NestJS — no OTel SDK required
Correlation id mixin for pino
Helps pass correlation-id across micro-services and logs
Injects a correlation id into every outgoing http request
A simple correlation-id generator
Foundation package for all hazo_* packages — errors, correlation ID, config, logger, debug, singletons, utils
A middleware for express, extending requests with a correlation id
OpenTelemetry tracing wrapper for Vizydrop/Targetprocess Node.js services. Provides auto-instrumentation, metric collection, and correlation ID capture middleware for Express and Koa.
NGRX Store feature to track tasks via correlation id
correlation middleware - adds correlation id to outgoing messages
Wrapper around pino logger that logs with correlation-id
Greentic operator CLI for local dev and demo orchestration.
Greentic operator CLI for local dev and demo orchestration.
Small helper crate to configure structured logging for IMMER's services using the tracing ecosystem.
Theme engine for rustio-admin: turns raw brand colors into a safe, computed tokens.css.
Django Admin, but for Rust. A small, focused admin framework.
Command-line tools for rustio-admin: project scaffolding, migrations, user management.
Proc-macros for rustio-admin (re-exported from the rustio-admin crate).
High-performance AI coding agent CLI - Rust port of Pi Agent
An Actix-web middleware component which synchronises a correlation ID for cross API request logging
Allows correlation tracking from request down the network stack
GlobalRequestId is a rails gem that makes your correlation id (X-REQUEST-ID header) globally avaiable during your entire http request.
{Marlowe}[https://github.com/KineticCafe/marlowe] is a Rack middleware that extracts or creates a request ID using a pre-defined header, permitting request correlation across multiple services. When using Rails, Marlowe automatically adds itself to the middleware before <tt>Rails::Rack::Logger</tt>. As of Marlowe 3.0, a Faraday middleware is provided (<tt>require 'marlowe/faraday'</tt>).
Semlogr integration for faraday providing features such as correlation id propogation.
Online logging solution (like [Datadog](https://www.datadoghq.com)) have drastically transform the way we log. An app will nowdays logs dozen (hundred) of logs per requests. The issue is often to correlate this logs, with the initiating request (or job) and add shared metadata on this logs. Here come `ContextualizedLogs`. The main idea is to enhance your logs from your controller (including `ContextualizedController`, which use a before action), which will add the params to your logs (and some metadata about the request itself, like `request.uuid`). This metadata are stored in a `ActiveSupport::CurrentAttributes` which is a singleton (reset per request). Each subsequent logs in this thread (request) will also be enriched with this metadata, making it easier to find all the logs associated with a request (`uuid`, `ip`, `params.xxx`). On top of this, logs can also be enriched by the ActiveRecord model they use (`create` or `find`) (models including `ContextualizedModel`). So any time a contextualized model is created or find, some metadata related to the model (`id`, ...) will also be added to the logs. Allowing you to find all logs which "touched" this models.
Geoptima is a suite of applications for measuring and locating mobile/cellular subscriber experience on GPS enabled smartphones. It is produced by AmanziTel AB in Helsingborg, Sweden, and supports many phone manufacturers, with free downloads from the various app stores, markets or marketplaces. This Ruby library is capable of reading the JSON format files produced by these phones and reformating them as CSV, GPX and PNG for further analysis in Excel. This is a simple and independent way of analysing the data, when compared to the full-featured analysis applications and servers available from AmanziTel. If you want to analyse a limited amount of data in excel, or with Ruby, then this GEM might be for you. If you want to analyse large amounts of data, from many subscribers, or over long periods of time then rather consider the NetView and Customer IQ applications from AmanziTel at www.amanzitel.com. Current features available in the library and the show_geoptima command: * Import one or many JSON files * Organize data by device id (IMEI) into datasets * Split by event type * Time ordering and time correlation (associate data from one event to another): ** Add GPS locations to other events (time window and interpolation algorithms) ** Add signal strenth, battery level, etc. to other events * Export event tables to CSV format for further processing in excel * Make and export GPS traces in GPX and PNG format for simple map reports The amount of data possible to process is limited by memory, since all data is imported in ruby data structures for procssing. If you need to process larger amounts of data, you will need a database-driven approach, like that provided by AmanziTel's NetView and Customer IQ solutions. This Ruby gem is actually used by parts of the data pre-processing chain of 'Customer IQ', but it not used by the main database and statistics engine that generates the reports.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.