A Public read only Grafana Dashboard with more insights into OpenCommit services #17

Open
opened 2026-09-14 10:26:20 +02:00 by benoit · 0 comments
Owner

Related to: opencommit/support#4

  1. What
    Create public, read-only Grafana dashboards showing platform statistics such as users, repositories, pull requests, signups, and relevant system metrics, including current data and historical trends.

  2. Why
    To improve transparency, demonstrate platform growth, support open-source observability tooling, and help the community understand platform evolution over time.

  3. Boundaries
    In-Scope:

  • Selecting useful, aggregated, non-sensitive metrics.
  • Creating and publishing historical Grafana dashboards.
  • Making the public dashboards strictly read-only.
  • Reviewing dashboards for privacy, security, and information-disclosure risks.
  • Documenting the metrics and their limitations.
  • Best-effort-only support.

Out-of-Scope:

  • Allowing public users to create, edit or otherwise modify dashboards, queries, or data sources.
  • Exposing personal, private, tenant-specific, or security-sensitive information.
  • Replacing internal monitoring dashboards.
  • Supporting bespoke dashboards created by users.
  • Supporting users on the use of these dashboards.
  1. Definition of Done
  • Public Grafana dashboards are available and strictly read-only.
  • Dashboards display relevant platform statistics and historical trends where feasible.
  • Metrics are aggregated and reviewed for privacy and security risks.
  • Public users cannot modify dashboards, queries, data sources, or permissions.
  • Dashboards are verified for reliability, readability, and appropriate access controls.
  • Documentation explains the purpose, scope, limitations, and safety considerations.
Related to: https://opencommit.eu/opencommit/support/issues/4 1. **What** Create public, read-only Grafana dashboards showing platform statistics such as users, repositories, pull requests, signups, and relevant system metrics, including current data and historical trends. 2. **Why** To improve transparency, demonstrate platform growth, support open-source observability tooling, and help the community understand platform evolution over time. 3. **Boundaries** **In-Scope:** - Selecting useful, aggregated, non-sensitive metrics. - Creating and publishing historical Grafana dashboards. - Making the public dashboards strictly read-only. - Reviewing dashboards for privacy, security, and information-disclosure risks. - Documenting the metrics and their limitations. - Best-effort-only support. **Out-of-Scope:** - Allowing public users to create, edit or otherwise modify dashboards, queries, or data sources. - Exposing personal, private, tenant-specific, or security-sensitive information. - Replacing internal monitoring dashboards. - Supporting bespoke dashboards created by users. - Supporting users on the use of these dashboards. 4. **Definition of Done** - [ ] Public Grafana dashboards are available and strictly read-only. - [ ] Dashboards display relevant platform statistics and historical trends where feasible. - [ ] Metrics are aggregated and reviewed for privacy and security risks. - [ ] Public users cannot modify dashboards, queries, data sources, or permissions. - [ ] Dashboards are verified for reliability, readability, and appropriate access controls. - [ ] Documentation explains the purpose, scope, limitations, and safety considerations.
Sign in to join this conversation.
No description provided.