Cube Metrics Client (Node.js + WebSockets)

100%

Cube Metrics Client (Node.js + WebSockets)

✓ Published0🌍 Public

Last edited Jan 4, 2012

Created on Jan 4, 2012

This example demonstrates a minimal Node.js client for streaming time-series metric data from a Cube server over WebSockets. It connects to the `/1.0/metric/get` endpoint, sends a JSON query requesting the sum of requests at five-minute intervals over a two-day period, and logs each incoming UTF-8 message until 762 responses arrive. The code uses the `websocket` library to manage the connection, sending a structured query and closing the socket after the expected number of messages is received.

AI-generated description

Similar vizzes

Loading thumbnail…

Node + MySQL + JSON

This example demonstrates a Node.js server that serves JSON data from a MySQL database to a front-end visualization. It sets the server’s timezone to UTC and uses Express to handle HTTP requests, with the `connect-gzip` middleware compressing responses. A GET endpoint for `/things/:id.json` queries a MySQL table named `things` via the `mysql` client, selecting fields like `name`, `favorite_color`, and `airspeed_velocity` based on the numeric ID from the URL, then returns the result as JSON. The code shows a direct pipeline from database query to API response, ready for consumption by a client-side chart.

Mmbostock

57% match

Loading thumbnail…

Gist 444255

This example demonstrates a Node.js server that queries MongoDB collections and logs their contents to the console, primarily as a backend testing or debugging tool. The code uses the `mongo.Db` and `mongo.Server` APIs to connect to a local MongoDB instance on port 27017, then defines HTTP routes via a `get()` handler. For each route, it retrieves documents from specific collections—`some-collection` and `another-collection` (the latter with a limit of 10)—and prints each item using `sys.puts` and `sys.inspect`. The visualization aspect is absent; the example focuses on database interaction and response handling.

CCaged

56% match

Loading thumbnail…

Trying out cubism

This example demonstrates a cubism-style visualization for time-series data, using a stacked area chart-like technique where five random walks (via `context.metric`) are rendered as horizons with negative and positive extents. The code leverages the `cubism` API from Square and D3.js (v3) to create interactive, zoomable panes with axes, a rule, and update timestamps. Data is generated procedurally with `Math.random()`, while the `context` handles appending values and shifting a secondary metric.

BBartekDu

56% match

Loading thumbnail…

Dataset #3: Netflow with GUI Info

This example displays summary statistics and raw JSON previews of a netflow dataset enriched with GUI interaction data. The page shows the row count, column count, and data size in kilobytes, followed by the first ten records in pretty-printed format. The code uses D3 v5’s `json()` function to fetch data.json, and `csvFormat()` from D3 to calculate the data’s size in kilobytes. The visualization presents the data source, which includes correlated keyboard, mouse, and GUI activity fields, in a straightforward textual format against a black terminal-style background.

Ffloresh

51% match

Loading thumbnail…

InfluxDb Measurement

This example demonstrates how to transform raw InfluxDB-style measurement data into a structured JSON payload. It shows a collection of sensor readings (such as pressure, temperature, and power) organized into InfluxDB line protocol objects, each with a measurement name, fields, and index-based tags. The code uses D3 v5’s `select` API to display the resulting JSON in the browser, while local ES6 modules handle data transformation. The `message.js` module iterates over the data keys and builds the output objects, which are rendered as text in the page’s message div.

SStrunck

50% match

Loading thumbnail…

Gist 05471e1965de232f4434a8624c8949dc

This example demonstrates a minimal Express.js server that serves player data from a SQLite database, exposing endpoints for retrieving all players or looking up a single player by email. The backend uses `express`, `body-parser`, and the `sqlite3` library, with an async utility function (`getPlayers` or `getPlayerByEmail`) handling database queries. Although no charting or visualization library is present, the code illustrates a typical API structure for feeding data to a front-end visualization. The root route returns a plain JSON message, while `/players` and `/playerByEmail` respond with JSON arrays or objects, showing how raw data would be delivered for subsequent graphical rendering.

WWill Carter

50% match

Loading thumbnail…

Fork of Seismograph - almost almost

This visualization presents a seismograph-style line chart displaying network throughput in megabits per second for four server endpoints (Partner, PCL, GOLAN, DriveU) over a two-minute period. Four colored lines, each representing an endpoint, trace the fluctuating data values across the timeline. The visualization uses a scrolling x-axis, which animates through the time series data to simulate a real-time monitoring view. The implementation uses d3.scaleTime, d3.scaleLinear, and a d3.line generator, with the x-axis positioned within a clipped group to enable the scrolling effect. Data comes from a CSV file containing per-second performance metrics.

PPiotr Paszek

50% match

Loading thumbnail…

Gist 660bf021ec250dfb10016d384d524bd7

This example shows a real-time chat application where users exchange messages through a Node.js server. The visualization tracks message flow and user activity using a force-directed graph rendered with D3.js’s `d3.forceSimulation` for node positioning and link physics. Each user appears as a node, with edges connecting them to messages they send, while color and size encode online status and message frequency. The code uses Socket.IO for live data updates and D3’s `transition.attrTween` to animate new nodes and links smoothly as events arrive, making the conversation pattern immediately visible.

FFrankieFabuloso

50% match