{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-236-compare-application-crash-frequency-against-actual-engagement-time/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-236-compare-application-crash-frequency-against-actual-engagement-time/", "slug": "dse-20260909-236-compare-application-crash-frequency-against-actual-engagement-time", "url": "https://update.dsesecurity.com/updates/dse-20260909-236-compare-application-crash-frequency-against-actual-engagement-time/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-236-compare-application-crash-frequency-against-actual-engagement-time.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-236-compare-application-crash-frequency-against-actual-engagement-time/" }, "title": "Compare application crash frequency against actual engagement time", "summary": "How should an endpoint team compare apps without mistaking raw crash counts for relative reliability?", "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-10T00:28:00+00:00", "modified_at": "2026-09-10T01:20:46+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 235, "potentially_affected": "Use this comparison for desktop application reliability, with the reported application identity and period recorded. Do not treat the report as a complete inventory of every background or rarely used application.", "dse_recommendation": "Compare crash frequency alongside usage and the number of affected devices.", "primary_source": { "name": "Application Reliability Report in Endpoint Analytics - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/endpoint-analytics/app-reliability", "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

Endpoint analytics calculates application mean time to failure from engagement duration divided by crash count over 14 days. Engagement includes active interaction and keep-alive activity, such as presenting. The report limits collected crash events to ten per app, device, and day. Its app-performance population also excludes applications without meaningful foreground usage and requires a sufficient active-device population. Microsoft Learn.

\n

Applicability

\n

Use this comparison for desktop application reliability, with the reported application identity and period recorded. Do not treat the report as a complete inventory of every background or rarely used application.

\n

DSE recommendation

\n

Compare crash frequency alongside usage and the number of affected devices. Ask the application owner to identify business impact before prioritizing a widely used app over a small but critical one. Inspect app-version and device detail for the affected population, and keep conclusions about the cause separate from the observed rate. Avoid ranking reliability using raw crashes alone.

\n

Verification

\n

Choose representative reported failures and reconcile their device timelines with the user’s experience. Check whether the compared applications had adequate usage and whether a severe recurring failure may be affected by the event cap. Test any proposed update or repair with the application owner and record the actual workflow result. Preserve the original period and population so a lower count after change is not mistaken for improvement merely because usage fell.

\n

Official references

\n

Microsoft Learn: Application Reliability Report in Endpoint Analytics.

", "content_text": "Source facts\nEndpoint analytics calculates application mean time to failure from engagement duration divided by crash count over 14 days. Engagement includes active interaction and keep-alive activity, such as presenting. The report limits collected crash events to ten per app, device, and day. Its app-performance population also excludes applications without meaningful foreground usage and requires a sufficient active-device population. Microsoft Learn.\nApplicability\nUse this comparison for desktop application reliability, with the reported application identity and period recorded. Do not treat the report as a complete inventory of every background or rarely used application.\nDSE recommendation\nCompare crash frequency alongside usage and the number of affected devices. Ask the application owner to identify business impact before prioritizing a widely used app over a small but critical one. Inspect app-version and device detail for the affected population, and keep conclusions about the cause separate from the observed rate. Avoid ranking reliability using raw crashes alone.\nVerification\nChoose representative reported failures and reconcile their device timelines with the user’s experience. Check whether the compared applications had adequate usage and whether a severe recurring failure may be affected by the event cap. Test any proposed update or repair with the application owner and record the actual workflow result. Preserve the original period and population so a lower count after change is not mistaken for improvement merely because usage fell.\nOfficial references\nMicrosoft Learn: Application Reliability Report in Endpoint Analytics.", "content_markdown": "## Source facts\n\nEndpoint analytics calculates application mean time to failure from engagement duration divided by crash count over 14 days. Engagement includes active interaction and keep-alive activity, such as presenting. The report limits collected crash events to ten per app, device, and day. Its app-performance population also excludes applications without meaningful foreground usage and requires a sufficient active-device population. [Microsoft Learn](https://learn.microsoft.com/en-us/intune/endpoint-analytics/app-reliability).\n\n## Applicability\n\nUse this comparison for desktop application reliability, with the reported application identity and period recorded. Do not treat the report as a complete inventory of every background or rarely used application.\n\n## DSE recommendation\n\nCompare crash frequency alongside usage and the number of affected devices. Ask the application owner to identify business impact before prioritizing a widely used app over a small but critical one. Inspect app-version and device detail for the affected population, and keep conclusions about the cause separate from the observed rate. Avoid ranking reliability using raw crashes alone.\n\n## Verification\n\nChoose representative reported failures and reconcile their device timelines with the user’s experience. Check whether the compared applications had adequate usage and whether a severe recurring failure may be affected by the event cap. Test any proposed update or repair with the application owner and record the actual workflow result. Preserve the original period and population so a lower count after change is not mistaken for improvement merely because usage fell.\n\n## Official references\n\n[Microsoft Learn: Application Reliability Report in Endpoint Analytics](https://learn.microsoft.com/en-us/intune/endpoint-analytics/app-reliability)." }, "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-236-compare-application-crash-frequency-against-actual-engagement-time/", "url": "https://update.dsesecurity.com/updates/dse-20260909-236-compare-application-crash-frequency-against-actual-engagement-time/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-236-compare-application-crash-frequency-against-actual-engagement-time/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Compare application crash frequency against actual engagement time", "item": "https://update.dsesecurity.com/updates/dse-20260909-236-compare-application-crash-frequency-against-actual-engagement-time/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-236-compare-application-crash-frequency-against-actual-engagement-time/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-236-compare-application-crash-frequency-against-actual-engagement-time/", "url": "https://update.dsesecurity.com/updates/dse-20260909-236-compare-application-crash-frequency-against-actual-engagement-time/", "headline": "Compare application crash frequency against actual engagement time", "description": "How should an endpoint team compare apps without mistaking raw crash counts for relative reliability?", "abstract": "How should an endpoint team compare apps without mistaking raw crash counts for relative reliability?", "articleBody": "Source facts\nEndpoint analytics calculates application mean time to failure from engagement duration divided by crash count over 14 days. Engagement includes active interaction and keep-alive activity, such as presenting. The report limits collected crash events to ten per app, device, and day. Its app-performance population also excludes applications without meaningful foreground usage and requires a sufficient active-device population. Microsoft Learn.\nApplicability\nUse this comparison for desktop application reliability, with the reported application identity and period recorded. Do not treat the report as a complete inventory of every background or rarely used application.\nDSE recommendation\nCompare crash frequency alongside usage and the number of affected devices. Ask the application owner to identify business impact before prioritizing a widely used app over a small but critical one. Inspect app-version and device detail for the affected population, and keep conclusions about the cause separate from the observed rate. Avoid ranking reliability using raw crashes alone.\nVerification\nChoose representative reported failures and reconcile their device timelines with the user’s experience. Check whether the compared applications had adequate usage and whether a severe recurring failure may be affected by the event cap. Test any proposed update or repair with the application owner and record the actual workflow result. Preserve the original period and population so a lower count after change is not mistaken for improvement merely because usage fell.\nOfficial references\nMicrosoft Learn: Application Reliability Report in Endpoint Analytics.", "datePublished": "2026-09-10T00:28:00+00:00", "dateModified": "2026-09-10T01:20:46+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-236-compare-application-crash-frequency-against-actual-engagement-time/" }, "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-236-compare-application-crash-frequency-against-actual-engagement-time/#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": "Compare application crash frequency against actual engagement time" }, "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": 235, "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": "Application Reliability Report in Endpoint Analytics - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/endpoint-analytics/app-reliability" } } ] } }