Tell us what works and what could be better. We read every submission.
@akilbekov·4 public vizzes
This visualization shows the migration path from RHEL 7.7 to CentOS 7.7 through a sequence of shell commands, rendered as a node-link diagram. The code uses `d3.forceSimulation` to lay out nodes representing individual commands, with links indicating the order of execution. It relies on a gist by akilbekov as the data source, parsing the command list from the migration script. The rendering highlights dependencies between steps such as package removals, repository switches, and system synchronization operations.
This visualization displays a Splunk configuration dashboard for monitoring Windows infrastructure, with separate inputs for 2008 and 2016 servers. The example shows how to collect OS logs, Active Directory events, DNS and DHCP data, plus host metrics through modular inputs. It demonstrates a time-series line chart comparing event volumes across different log sources, rendered with D3.js, highlighting the flow of data from various Windows event logs, scripted inputs, and performance monitors into Splunk indexes such as wineventlog, msad, and windows.
This example shows a Splunk configuration for collecting Windows system data, including event logs, performance counters, and scripted inputs. The `input.conf` file defines stanzas for WinEventLog, WinHostMon, WinNetMon, and perfmon collection, with specific intervals and index assignments. The `props.conf` file uses SEDCMD regex transformations to clean and format Windows event log data before indexing. The configuration relies on Splunk's built-in monitoring APIs rather than a visualization library, directing data into indexes such as wineventlog, windows, and perfmon.
This example demonstrates four idiomatic patterns for testing React components, organized by purity: basic rendering, stateless interactions, stateful interactions, and instance methods. It shows how to structure test setup with a `getComponent` helper that provides default props while allowing per-test overrides. The code uses Mocha, Chai, Sinon, React’s `TestUtils.renderIntoDocument`, `ReactDOM.render`, and `ReactDOM.findDOMNode` to render components and simulate user events, with re-rendering for stateful cases. The patterns cover asserting prop-driven output, callback invocation, state changes, and direct method calls.