{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation/", "slug": "dse-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation", "url": "https://update.dsesecurity.com/updates/dse-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation/" }, "title": "Choose how expired Service Fabric health reports affect evaluation", "summary": "A report can disappear at expiry or remain as an error; an infinite lifetime does neither automatically.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "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-10T00:25:58+00:00", "modified_at": "2026-09-10T02:01:55+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 226, "potentially_affected": "Azure Service Fabric applications with custom periodic health reports.", "dse_recommendation": "Define report lifetime and expiry behavior as part of the reporter's failure-detection contract.", "primary_source": { "name": "Health monitoring in Service Fabric - Azure Service Fabric | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-health-introduction", "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

A Service Fabric health report’s TimeToLive defines its validity and defaults to infinite. With RemoveWhenExpired set to true, an expired report is removed and no longer affects entity health. With the setting false, expiry is evaluated as an error, representing a reporter that failed to refresh its state.

\n

A retained expired report makes the entity’s evaluation Error regardless of the report’s original health state. Queries expose IsExpired only for retained events; removed expired reports are no longer returned. Microsoft Learn.

\n

Applicability

\n

Identify each custom reporter, property, expected refresh cadence and intended response to silence. Distinguish a temporary observation from a watchdog that must keep reporting.

\n

DSE recommendation

\n

DSE recommends choosing lifetime and expiry handling together. For a periodic watchdog, explicitly decide whether missing reports should raise an error instead of silently disappearing. For a temporary event, define how it will clear. Avoid leaving the default infinite lifetime unexamined when the operational requirement is freshness.

\n

Verification

\n

In a controlled environment, stop refreshing a test report and observe the entity after its configured lifetime. Compare both the returned event and aggregated health with the intended behavior. Resume reporting and verify recovery. Record the source, property and settings so a stale OK report is not accepted as proof that the monitored component is still healthy.

\n

Official references

\n

Microsoft Learn: Health monitoring in Service Fabric. Source retrieved September 9, 2026.

", "content_text": "Source facts\nA Service Fabric health report’s TimeToLive defines its validity and defaults to infinite. With RemoveWhenExpired set to true, an expired report is removed and no longer affects entity health. With the setting false, expiry is evaluated as an error, representing a reporter that failed to refresh its state.\nA retained expired report makes the entity’s evaluation Error regardless of the report’s original health state. Queries expose IsExpired only for retained events; removed expired reports are no longer returned. Microsoft Learn.\nApplicability\nIdentify each custom reporter, property, expected refresh cadence and intended response to silence. Distinguish a temporary observation from a watchdog that must keep reporting.\nDSE recommendation\nDSE recommends choosing lifetime and expiry handling together. For a periodic watchdog, explicitly decide whether missing reports should raise an error instead of silently disappearing. For a temporary event, define how it will clear. Avoid leaving the default infinite lifetime unexamined when the operational requirement is freshness.\nVerification\nIn a controlled environment, stop refreshing a test report and observe the entity after its configured lifetime. Compare both the returned event and aggregated health with the intended behavior. Resume reporting and verify recovery. Record the source, property and settings so a stale OK report is not accepted as proof that the monitored component is still healthy.\nOfficial references\nMicrosoft Learn: Health monitoring in Service Fabric. Source retrieved September 9, 2026.", "content_markdown": "## Source facts\n\nA Service Fabric health report’s TimeToLive defines its validity and defaults to infinite. With RemoveWhenExpired set to true, an expired report is removed and no longer affects entity health. With the setting false, expiry is evaluated as an error, representing a reporter that failed to refresh its state.\n\nA retained expired report makes the entity’s evaluation Error regardless of the report’s original health state. Queries expose IsExpired only for retained events; removed expired reports are no longer returned. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-health-introduction).\n\n## Applicability\n\nIdentify each custom reporter, property, expected refresh cadence and intended response to silence. Distinguish a temporary observation from a watchdog that must keep reporting.\n\n## DSE recommendation\n\nDSE recommends choosing lifetime and expiry handling together. For a periodic watchdog, explicitly decide whether missing reports should raise an error instead of silently disappearing. For a temporary event, define how it will clear. Avoid leaving the default infinite lifetime unexamined when the operational requirement is freshness.\n\n## Verification\n\nIn a controlled environment, stop refreshing a test report and observe the entity after its configured lifetime. Compare both the returned event and aggregated health with the intended behavior. Resume reporting and verify recovery. Record the source, property and settings so a stale OK report is not accepted as proof that the monitored component is still healthy.\n\n## Official references\n\n[Microsoft Learn: Health monitoring in Service Fabric](https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-health-introduction). Source retrieved September 9, 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-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation/", "url": "https://update.dsesecurity.com/updates/dse-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Choose how expired Service Fabric health reports affect evaluation", "item": "https://update.dsesecurity.com/updates/dse-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation/", "url": "https://update.dsesecurity.com/updates/dse-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation/", "headline": "Choose how expired Service Fabric health reports affect evaluation", "description": "A report can disappear at expiry or remain as an error; an infinite lifetime does neither automatically.", "abstract": "A report can disappear at expiry or remain as an error; an infinite lifetime does neither automatically.", "articleBody": "Source facts\nA Service Fabric health report’s TimeToLive defines its validity and defaults to infinite. With RemoveWhenExpired set to true, an expired report is removed and no longer affects entity health. With the setting false, expiry is evaluated as an error, representing a reporter that failed to refresh its state.\nA retained expired report makes the entity’s evaluation Error regardless of the report’s original health state. Queries expose IsExpired only for retained events; removed expired reports are no longer returned. Microsoft Learn.\nApplicability\nIdentify each custom reporter, property, expected refresh cadence and intended response to silence. Distinguish a temporary observation from a watchdog that must keep reporting.\nDSE recommendation\nDSE recommends choosing lifetime and expiry handling together. For a periodic watchdog, explicitly decide whether missing reports should raise an error instead of silently disappearing. For a temporary event, define how it will clear. Avoid leaving the default infinite lifetime unexamined when the operational requirement is freshness.\nVerification\nIn a controlled environment, stop refreshing a test report and observe the entity after its configured lifetime. Compare both the returned event and aggregated health with the intended behavior. Resume reporting and verify recovery. Record the source, property and settings so a stale OK report is not accepted as proof that the monitored component is still healthy.\nOfficial references\nMicrosoft Learn: Health monitoring in Service Fabric. Source retrieved September 9, 2026.", "datePublished": "2026-09-10T00:25:58+00:00", "dateModified": "2026-09-10T02:01:55+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation/" }, "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-20260909-358-choose-how-expired-service-fabric-health-reports-affect-evaluation/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Choose how expired Service Fabric health reports affect evaluation" }, "articleSection": [ "Cybersecurity", "Networks & Infrastructure" ], "keywords": [ "Cybersecurity", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 226, "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 monitoring in Service Fabric - Azure Service Fabric | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-health-introduction" } } ] } }