Description is missing metrics

[DavidRawling]

Details on the following metrics are missing from the description of this cmdlet:

• AggregatedAverageNormalizedIOPS
• AggregatedAverageLatency
• AggregatedDiskDataRead
• AggregatedDiskDataWritten
• AggregatedNormalizedIOCount
• HardDiskMetrics / AverageNormalizedIOPS
• HardDiskMetrics / AverageLatency
• HardDiskMetrics / DiskDataRead
• HardDiskMetrics / DiskDataWritten
• HardDiskMetrics / NormalizedIOCount

In particular, the units for each are important (for example is DiskDataRead measured in Bytes, KB or MB? Is Latency in seconds, milliseconds or microseconds?).

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 1db41d68-3011-69f0-43d4-500641122086
• Version Independent ID: e1cd47ec-aba9-b0b9-572d-8f846653d701
• Content: Measure-VM (hyper-v)
• Content Source: docset/windows/hyper-v/measure-vm.md
• Product: w10
• GitHub Login: @coreyp-at-msft
• Microsoft Alias: coreyp

[o0nj]

@officedocsbot assign @e0i

[o0nj]

@DavidRawling

The issue is being routed to Windows PowerShell writing team for investigation. You'll be notified with relevant updates as content gets updated.

Thank you for providing feedback.

[schittli]

Does M$ really need 2 years to describe performance metrics? What a shame!

[officedocspr5]

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.

As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.

If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.

With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.

Here's what the new experience looks like.

Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.

First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful	Article was unhelpful

Finally, select Submit and you're done!