3.1 Aggregating Data

What

The FileWave dashboard can show raw device data, but aggregated data is what gives you the quick summary. Aggregation rolls many records into something easier to read, such as counts by version, model, or status.

When/Why

Use aggregation when you need the big picture instead of a long list. For example, if you are rolling Java from build 183 to build 196, a per-device report shows every record, but an aggregated view shows how many devices are still on each version. That makes rollout progress much easier to understand at a glance.

How

Choose the walkthrough that matches the data you want to chart. Using Grafana for Data Aggregation shows how to build a grouped visualization directly from a FileWave report. For the Prometheus-based workflow, follow the sequence below.

Before configuring the Prometheus job, prepare an Inventory Report with the devices and fields you intend to count and group. Keep its report ID and preview results available for comparison. The server-side configuration steps require access to a self-managed FileWave Server; hosted customers should ask FileWave Technical Support to handle those steps.

1. Group FileWave Report Data with Prometheus: select the report, count field and grouping field, then configure the scrape job.
2. Test the Prometheus scrape: check that the target exists and inspect any scrape error.
3. Explore the aggregate data: compare the labels and counts with the source report. A successful scrape alone does not establish that you counted the intended devices.
4. Create the data panel: build and save the visualization after the grouped result matches the report.