{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends/", "slug": "dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends", "url": "https://update.dsesecurity.com/updates/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends/" }, "title": "Capture Health Service metrics as timed snapshots, not historical trends", "summary": "What context should accompany a Storage Spaces Direct Health Service performance report?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:14:38+00:00", "modified_at": "2026-09-08T18:26:31+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 2, "word_count": 221, "potentially_affected": "Use this review when collecting cluster metrics for an investigation or capacity discussion.", "dse_recommendation": "Record timestamps and cluster membership with each captured report.", "primary_source": { "name": "Health Service reports", "url": "https://learn.microsoft.com/en-us/windows-server/failover-clustering/health-service-reports", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

Microsoft’s Health Service reports provide live capacity and performance metrics aggregated across cluster nodes, with membership detection. The values represent the point in time at which they are collected. The documented object model distinguishes the storage subsystem, nodes, data volumes, and Health Service. Its streaming example receives successive metric samples and handles the end of the stream separately. Microsoft documentation.

\n

Applicability

\n

Use this review when collecting cluster metrics for an investigation or capacity discussion. Identify the cluster, requested objects, sampling time, and workload conditions. Decide whether a single observation or a retained sequence is needed.

\n

DSE recommendation

\n

Record timestamps and cluster membership with each captured report. Select a consistent observation interval when the question concerns change over time, and arrange an approved destination for retained samples. Ask the storage owner to define the workload context needed to interpret the values. Keep a missing sample distinguishable from a measured low value in the record.

\n

Verification

\n

Compare repeated observations collected under the agreed method and verify that they refer to the intended cluster and volumes. Check the handling of an interrupted collection session rather than assuming continuous coverage. Document gaps, membership changes, and workload differences alongside any conclusion. Preserve the original samples so a later reviewer can separate observations from interpretation.

\n

Official references

\n

Microsoft Learn: Health Service reports. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft’s Health Service reports provide live capacity and performance metrics aggregated across cluster nodes, with membership detection. The values represent the point in time at which they are collected. The documented object model distinguishes the storage subsystem, nodes, data volumes, and Health Service. Its streaming example receives successive metric samples and handles the end of the stream separately. Microsoft documentation.\nApplicability\nUse this review when collecting cluster metrics for an investigation or capacity discussion. Identify the cluster, requested objects, sampling time, and workload conditions. Decide whether a single observation or a retained sequence is needed.\nDSE recommendation\nRecord timestamps and cluster membership with each captured report. Select a consistent observation interval when the question concerns change over time, and arrange an approved destination for retained samples. Ask the storage owner to define the workload context needed to interpret the values. Keep a missing sample distinguishable from a measured low value in the record.\nVerification\nCompare repeated observations collected under the agreed method and verify that they refer to the intended cluster and volumes. Check the handling of an interrupted collection session rather than assuming continuous coverage. Document gaps, membership changes, and workload differences alongside any conclusion. Preserve the original samples so a later reviewer can separate observations from interpretation.\nOfficial references\nMicrosoft Learn: Health Service reports. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft’s Health Service reports provide live capacity and performance metrics aggregated across cluster nodes, with membership detection. The values represent the point in time at which they are collected. The documented object model distinguishes the storage subsystem, nodes, data volumes, and Health Service. Its streaming example receives successive metric samples and handles the end of the stream separately. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/failover-clustering/health-service-reports).\n\n## Applicability\n\nUse this review when collecting cluster metrics for an investigation or capacity discussion. Identify the cluster, requested objects, sampling time, and workload conditions. Decide whether a single observation or a retained sequence is needed.\n\n## DSE recommendation\n\nRecord timestamps and cluster membership with each captured report. Select a consistent observation interval when the question concerns change over time, and arrange an approved destination for retained samples. Ask the storage owner to define the workload context needed to interpret the values. Keep a missing sample distinguishable from a measured low value in the record.\n\n## Verification\n\nCompare repeated observations collected under the agreed method and verify that they refer to the intended cluster and volumes. Check the handling of an interrupted collection session rather than assuming continuous coverage. Document gaps, membership changes, and workload differences alongside any conclusion. Preserve the original samples so a later reviewer can separate observations from interpretation.\n\n## Official references\n\n[Microsoft Learn: Health Service reports](https://learn.microsoft.com/en-us/windows-server/failover-clustering/health-service-reports). Source reviewed September 8, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends/", "url": "https://update.dsesecurity.com/updates/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Capture Health Service metrics as timed snapshots, not historical trends", "item": "https://update.dsesecurity.com/updates/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends/", "url": "https://update.dsesecurity.com/updates/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends/", "headline": "Capture Health Service metrics as timed snapshots, not historical trends", "description": "What context should accompany a Storage Spaces Direct Health Service performance report?", "abstract": "What context should accompany a Storage Spaces Direct Health Service performance report?", "articleBody": "Source facts\nMicrosoft’s Health Service reports provide live capacity and performance metrics aggregated across cluster nodes, with membership detection. The values represent the point in time at which they are collected. The documented object model distinguishes the storage subsystem, nodes, data volumes, and Health Service. Its streaming example receives successive metric samples and handles the end of the stream separately. Microsoft documentation.\nApplicability\nUse this review when collecting cluster metrics for an investigation or capacity discussion. Identify the cluster, requested objects, sampling time, and workload conditions. Decide whether a single observation or a retained sequence is needed.\nDSE recommendation\nRecord timestamps and cluster membership with each captured report. Select a consistent observation interval when the question concerns change over time, and arrange an approved destination for retained samples. Ask the storage owner to define the workload context needed to interpret the values. Keep a missing sample distinguishable from a measured low value in the record.\nVerification\nCompare repeated observations collected under the agreed method and verify that they refer to the intended cluster and volumes. Check the handling of an interrupted collection session rather than assuming continuous coverage. Document gaps, membership changes, and workload differences alongside any conclusion. Preserve the original samples so a later reviewer can separate observations from interpretation.\nOfficial references\nMicrosoft Learn: Health Service reports. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:38+00:00", "dateModified": "2026-09-08T18:26:31+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-153-capture-health-service-metrics-as-timed-snapshots-not-historical-trends/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Capture Health Service metrics as timed snapshots, not historical trends" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 221, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Health Service reports", "url": "https://learn.microsoft.com/en-us/windows-server/failover-clustering/health-service-reports" } } ] } }