content_telemetry 1.0.0-alpha3

Overview

This alpha release significantly expands Content Telemetry by adding route-level
performance insights, polishing entity performance reports, and hardening the
telemetry aggregation pipeline.

New features

• Route performance reporting
  
  A new administrative report shows performance metrics aggregated by route
  (e.g. user.login, view.frontpage.page_1), including
  average render time and sample counts.
• Entity-level performance tabs
  
  Nodes now expose a dedicated Performance tab displaying health status,
  trends, metric cards, and detailed aggregated metrics.
• Polished performance UI
  
  Performance pages now use structured layouts, metric cards, status indicators,
  and consistent numeric alignment for improved readability and usability.

Telemetry & aggregation improvements

• Hardened hourly and daily aggregation with strict idempotency and batch limits
  to ensure safe cron execution.
• Clear separation between raw telemetry samples and aggregated performance data.
• Improved handling of missing or insufficient historical data.

Developer notes

• Route, view, and node telemetry are now clearly distinguished via
  entity_type.
• View and block performance pages in core UI are acknowledged as placeholders
  and are not yet populated with telemetry data.
• This release focuses on correctness, observability, and API stability ahead
  of advanced analytics features.

Known limitations

• View and block performance pages currently display placeholder messages only.
  Dedicated reports for these entities are planned for a future alpha.
• Performance data requires cron to run in order to aggregate telemetry samples.

Upgrade notes

• Run database updates after upgrading.
• Ensure cron is running to populate aggregated performance tables.