DC splunk

100%

✓ Published0🌍 Public

Last edited Sep 2, 2019

Created on Sep 2, 2019

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.

AI-generated description

Similar vizzes

Loading thumbnail…

Windows inputs and props conf, general

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.

Aakilbekov

66% match

Loading thumbnail…

test

This visualization shows an animated scatterplot of server monitoring data, where each point represents a server positioned by its ID and log file size, with color indicating the server pool. The animation cycles through time-stamped snapshots from the accompanying CSV, updating point positions and sizes to reflect changes in SAP start-up log file sizes across hosts. Rendered as an SVG, the chart uses a smooth linear transition over a 3-second duration, with 15 clone frames to create a fluid effect. The data highlights differences across Linux and AIX systems, with labeled pools like "Blade_Test" and "DEV/QA".

CCBasis

58% match

Loading thumbnail…

Overview - Compact Event Sequences

This visualization presents a compact overview of event sequences from Windows application activity, where each row represents a single process event chain and each column indicates a UI element change over time. The event data, sourced from `data.json`, includes timestamps, application names like Word and PowerPoint, and window or pane class names. Built with D3 v5, the SVG rendering uses a color scale based on the distribution of pane class names across the dataset to encode recurring patterns. Rows are displayed as sequences of colored rectangles, and hovering over a row highlights that specific event sequence. The code utilizes D3’s `hierarchy` function to structure each event’s nested children and `scaleSequential` with an `interpolateRdBu` color gradient for visual encoding.

Ffloresh

58% match

Loading thumbnail…

Gist 7729027

This visualization shows the architecture of a multi-datacenter Node.js deployment, mapping how traffic flows from clients through load balancers, Apache, and hapi.js servers to legacy Java services and analytics pipelines. The diagram uses the `d3.forceSimulation` layout to position nodes representing processes, plugins, and message queues, with edges linking components like `good`, `elmer`, and `prospector`. The code highlights the `services-us-legacy` proxy plugin and its route configuration, while the analytics flow into RabbitMQ, MongoDB, and Splunk is traced from the raw gistfile1.md data.

Aalessioalex

57% 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

57% match

Loading thumbnail…

Aggregated Event Sequences with GUI Histograms

This visualization aggregates event sequences from network flow data, showing compact event sequence strips in the center alongside histograms of destination IP, port, and source IP attributes on the left. Users can filter events by typing a regular expression, which highlights matching sequence elements and updates a percentage counter. Selecting a sequence displays its event details, including name, content name, and content type, on the right. The implementation uses d3.hierarchy, d3.scaleBand, d3.scaleLinear, d3.axisBottom, d3.axisLeft, and SVG rendering with tooltips.

Ffloresh

57% match

Loading thumbnail…

dc.js Experiment

This dc.js experiment visualizes earthquake data from New Zealand’s Geonet service, displaying events by magnitude and depth as bar charts, a line chart of events per hour, and a sortable data table. Built with crossfilter for multidimensional filtering, dc.js coordinates the charts, while D3.js handles SVG rendering and animated transitions. The dashboard loads a CSV file containing earthquake records and supports interactive filtering across all visualizations simultaneously.

Dd3noob

57% match

Loading thumbnail…

Gist 158909

This visualization parses monit log files from Engine Yard to display the status of a scheduled event processor process. It uses `d3.forceSimulation` to position nodes in a network graph, where each node represents a monitored service or host entry parsed from the plain-text log. The rendering relies on SVG elements driven by D3’s enter/update/exit data joins, with tooltips showing process details like PID and monitoring mode. The example specifically highlights the `scheduled_event_processor_crusher` service, using the log’s runtime constants and service list as the data source.

XXXX

56% match