Search Results for "http-client"

Node.js client for Elasticsearch. The client versioning follows the Elastic Stack versioning, this means that major, minor, and patch releases are done following a precise schedule that often does not coincide with the Node.js release times. Language clients are forward compatible; meaning that clients support communicating with greater or equal minor versions of Elasticsearch.

...It provides block-based document editing, a custom object model for data types, and a rich UI for organizing knowledge like a personal wiki. This repo includes the client logic that powers the app’s core experience.

ioredis is a robust, full-featured Redis client that is used in the world's biggest online commerce company Alibaba and many other awesome companies. Full-featured. It supports Cluster, Sentinel, Streams, Pipelining and of course Lua scripting & Pub/Sub (with the support of binary messages). High performance. Delightful API. It works with Node callbacks and Native promises. Transformation of command arguments and replies.

...UI-Router states are hierarchical; states can be nested inside other states, forming a tree. Child states may inherit data and behavior (such as authentication) from their parent states. A client-side router updates the browser URL as the user nagivates through the single page app. Conversely, changes to the browser’s URL can drive navigation of the app, enabling a user to create deep-links (i.e., bookmarks) to areas deep within the application.

...End-to-end distributed tracing. Service topology analysis, service-centric observability and API dashboards. Java, .Net Core, PHP, NodeJS, Golang, LUA, Rust, C++, Client JavaScript and Python agents with active development and maintenance. Rover agent works as a metrics collector and profiler powered by eBPF to diagnose CPU and network performance. 100+ billion telemetry data could be collected and analyzed from one SkyWalking cluster. Metrics, Traces, and Logs from mature ecosystems are supported, e.g. ...

...Log messages are tagged with stream and source information based on user configuration. log.io has no persistence layer. File inputs are informed of file changes via inotify, and log messages hop from input to server to web client via TCP and socket.io, respectively. log.io uses a stateless TCP API to receive log messages. Writing a third party harvester is easy. Open a TCP connection to the server and begin writing properly formatted messages to the socket. Input paths can be a file path, directory path or a glob. Additionally, watcher options can be provided for more fine-grained control over file watching mechanics and performance. ...