Skip to content

ROX-34665: Add Scans per Day by Namespace panel to cluster overview#340

Open
ebensh wants to merge 2 commits into
masterfrom
rox-34665-scans-per-day
Open

ROX-34665: Add Scans per Day by Namespace panel to cluster overview#340
ebensh wants to merge 2 commits into
masterfrom
rox-34665-scans-per-day

Conversation

@ebensh
Copy link
Copy Markdown
Contributor

@ebensh ebensh commented May 15, 2026

Summary

  • Adds a new "Scans per Day by Namespace" table panel to the rhacs-cluster-overview Grafana dashboard
  • Panel placed directly after the Scanner Overview Table at full width (w=24)
  • Uses increase(rox_central_scan_duration_count[1d]) with matrix transform to show daily scan counts per namespace as date columns
image

Details

The panel uses the existing $_relativeTime and $_timeShift dashboard variables to control the time window. Results are formatted as a pivot table with namespaces as rows and dates (YYYY-MM-DD) as columns.

Test plan

  • Verify panel renders correctly in Grafana staging
  • Confirm date columns populate with scan count data
  • Check panel positioning relative to Scanner Overview Table and Certificate Expiry section

🔗 ROX-34665

…ashboard

Add table panel showing daily scan counts broken down by namespace to
rhacs-cluster-overview dashboard, placed after Scanner Overview Table.
Uses increase(rox_central_scan_duration_count[1d]) with matrix transform
to display dates as columns.
@ebensh ebensh requested a review from a team as a code owner May 15, 2026 09:52
@ebensh ebensh requested review from kovayur and kurlov and removed request for a team and kovayur May 15, 2026 09:52
@GrimmiMeloni
Copy link
Copy Markdown

Could we also chart this to allow spotting spikes quickly?

@@ -0,0 +1,12 @@
{
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add this file to .gitignore?

@kovayur
Copy link
Copy Markdown
Contributor

kovayur commented May 18, 2026

Agree with @GrimmiMeloni , a chart would be more representative than a table

@ebensh
Copy link
Copy Markdown
Contributor Author

ebensh commented May 18, 2026

Could we also chart this to allow spotting spikes quickly?

Agree with @GrimmiMeloni , a chart would be more representative than a table

I originally had a continuous plot of the metric and asked about this but the answer I got was:

I wanted to answer how many scans does a customer do in a given day. Just to know how their usage patterns look like.

So I converted to a table aligned to midnight for the daily counts. I can of course go back to a simple increase()[1d] for the rolling amount. Do we want the table and the plot or just the plot?

@GrimmiMeloni
Copy link
Copy Markdown

I think just the plot would be fine. It's ok if it only shows the daily number like in the table. The whole idea was to simply have something to "eyeball" the usage patterns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants