Aggregation for reporting dashboards in MongoDB - Step-by-Step Execution

Concept Flow - Aggregation for reporting dashboards

Start with collection

↓

Apply $match to filter data

↓

Use $group to aggregate

↓

Optionally $project to shape output

↓

Sort or limit results

↓

Output dashboard-ready data

Data flows from raw collection through filtering, grouping, shaping, and sorting to produce dashboard-ready summaries.

Execution Sample

MongoDB

db.sales.aggregate([
  {$match: {region: 'East'}},
  {$group: {_id: '$product', totalSales: {$sum: '$amount'}}},
  {$sort: {totalSales: -1}}
])

This query filters sales to the East region, sums sales by product, and sorts products by total sales descending.

Execution Table

Step	Stage	Input Documents	Action	Output Documents
1	$match	All sales documents	Filter where region = 'East'	Only sales from East region
2	$group	Filtered East sales	Group by product, sum amounts	One document per product with totalSales
3	$sort	Grouped documents	Sort by totalSales descending	Documents ordered by totalSales high to low
4	End	Sorted documents	Return results	Final aggregated data for dashboard

💡 Aggregation pipeline completes after $sort stage, producing dashboard-ready summary.

Variable Tracker

Variable	Start	After $match	After $group	After $sort	Final
documents	All sales	East region sales only	Grouped by product with totalSales	Sorted by totalSales descending	Dashboard summary data

Key Moments - 3 Insights

Why do we use $match first in the pipeline?

Using $match first reduces the number of documents early, making grouping and sorting faster and more efficient, as shown in execution_table step 1.

What does $group do with the _id field?

$group uses _id to define groups; here, _id is set to product, so sales are summed per product, as seen in execution_table step 2.

Why sort after grouping and not before?

Sorting after grouping orders the aggregated results, not raw data. Sorting raw data first wouldn't order the final totals correctly, as shown in execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output after the $match stage?

A All sales documents

B Sales documents only from the East region

C Grouped sales by product

D Sorted sales by total amount

💡 Hint

Check execution_table row 1 under Output Documents column.

At which step does the aggregation pipeline group sales by product?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at execution_table Stage column and find where $group is applied.

If we remove the $match stage, what will happen to the output?

A Only East region sales will be included

B No documents will be returned

C All sales from all regions will be grouped and sorted

D The pipeline will fail

💡 Hint

Refer to variable_tracker showing documents after $match and consider what happens if $match is skipped.

Concept Snapshot

Aggregation pipelines process data step-by-step.
Start with $match to filter documents.
Use $group to aggregate data by keys.
Optionally $project to format output.
Sort or limit results last.
This produces dashboard-ready summaries.

Full Transcript

Aggregation pipelines in MongoDB help create reporting dashboards by processing data step-by-step. First, $match filters documents to include only relevant data, like sales from a specific region. Next, $group aggregates data by a key, such as product, summing sales amounts. Then, $sort orders the aggregated results, for example by total sales descending. Finally, the pipeline outputs the processed data ready for dashboard display. This flow improves efficiency and clarity in reporting.