What we measure depends on what we want to know which in turn depends on the product and its context. Most metrics are dangerous, inaccurate, badly communicated and misused or abused, so I’d say the default position should be to measure things that are known quantities and make very limited decisions based on them (e.g. time taken to fully run a tool if we’re trying to reduce the time to fully run a tool). There’s no top 5 because the concept would be flawed. I could ask what are the top 5 vehicles… top 5 for what? Fuel efficiency? Cost? How high it can safely fly? Resistance to anti-tank rounds?
Things that are often counted such as bugs or test cases or person hours are a complete waste of time to track as a whole but can yield more interesting results when they’re categorised. For example knowing there are “10 bugs” (i.e. 10 bug reports physically written down or typed out) is pointless but knowing what areas of the product tend to generate a higher proportion of bug reports is less pointless.