MarketSquare / MarketSquare/robotframework-dashboard

[Improvement] Global Aggregated Dashboard for Multi-Project Monitoring

Open
#294 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
HTML
Stars
87
Forks
21
Avg merge
14h 55m
Merged PRs (30d)
13

Description

First of all, congratulations to everyone involved in the development of RobotDashboard.
After testing the new version extensively, I am genuinely impressed with the overall quality and completeness of the solution.
The solution is very well designed and will be adopted in our projects going forward.

At the moment, we are running a setup where a central server initializes independent RobotDashboard instances per project. This allows us to maintain isolated dashboards, each customized according to the specific requirements of the respective project.

We would like to suggest the introduction of an additional higher-level dashboard layer capable of aggregating information from multiple active project dashboards/servers.

The idea would be to provide:
* A centralized management dashboard
* Cross-project KPI visualization
* Aggregated metrics and reporting
* Consolidated tables/data from all monitored projects
* High-level visibility without needing to access each individual project dashboard separately

Examples of useful aggregated information:
* Overall execution status across projects
* Pass/fail trends
* Execution duration metrics
* Environment health/status
* Unified reporting views
* Custom organizational KPIs

Although this may extend beyond the original scope of RobotDashboard, it would provide significant value from a management and operational perspective, especially for organizations managing multiple independent projects.
This would greatly simplify monitoring activities and improve visibility at a portfolio/program level.

Once again, congratulations for the excellent work and for building such a flexible and extensible solution.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified in the issue, so start by mapping how the existing project dashboards expose their data and how dashboard views are assembled. Done would require an agreed design and working centralized views for cross-project status, metrics, reporting, and organizational KPIs.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
analytics, data-visualization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.