Insights aggregates what's been happening — who is running what, how long it takes, and what your compute is costing. It exists at two scopes, and they answer different questions.
Organization insights
Under /<org>/insights, covering every project in the organization.
Training Request Activity
Training requests over time, plus a TR Leaderboard of who is creating them. Useful for seeing whether review is actually happening or whether requests are piling up unreviewed.
Run Activity
Runs over time, a Run Leaderboard, and a histogram of compute time per training request. The histogram is the interesting one: it shows the distribution rather than an average, so a handful of very long runs don't hide behind a reasonable-looking mean.
Compute Utilization
Only at the organization scope, because compute targets are organization-level. Dedicated and on-demand targets are reported separately, since the questions differ.
Project insights
Under /<org>/<project>/insights, the same Training Request Activity and Run Activity views scoped to one project. There's no utilization view here — compute isn't owned by a project, so there's nothing project-shaped to report.
Use project insights to look at one workstream; use organization insights to compare across them or to make decisions about hardware.