Metrics / Reports to Management

They should know about the organizational impediments Scrum Teams face when trying to provide value each Sprint, and which senior leadership are best positioned to remove.

What, exactly, does "Management" want to know? Any metrics should be selected based on the information needs of stakeholders.

I'd also suggest that the Sprint Review is the opportunity for the Product Owner to invite key stakeholders, including management, to get insights into what the Developers have been doing, the current state of the Product Backlog, reviewing timelines and budgets and release plans, and reviewing changes in users and use cases for the product. It could be possible that many of management's questions can be answered without metrics and reports attending the Sprint Review that is no more than 4 hours every Sprint.

If you are using a Kanban + scrum approach (PSK), use a montecarlo to show where the forecast stands in relation to what's left.

You should certainly make sure they see the product goal and probably the various sprint goals.  Lots of people use story points and velocity, but I prefer a Kanban flow approach.

The ultimate question is what is management trying to know about?  What are they trying to control (hopefully not much).  The EBM metrics can help a a place to look, but the biggest question is not what reports and metrics, but what are they looking to see and why.