There is a recent thread around this topic, you want to get a Pro subscription and watch Jenny’s talk as linked above by Emna though.
Here is the recent related thread https://club.ministryoftesting.com/t/qa-statistics-to-show-qa-is-doing-its-job
/edit:
My main input on the broader agile health thing is to count how many experiments you have done in your sprints. Look at your retrospectives actions/notes and look for repeat actions that nobody seems to ever act upon (you are capturing a retrospective for every single sprint aren’t you, else this exercise is pointless?) Jira has a nice retro notes thing when you close a sprint, we don’t use it, a wiki page is perfectly fine, or even simpler to just add a big note below the miro board (/disclaimer: other tools and products are available.)
Some experiments must run for 2 or more sprints in order to cut out side-effects, and mostly experiments prove you have healthy communication going within your team. No experiments = no agile.