---
title: "How Metadata and Runtime Telemetry Reveal Which Enterprise System Problems to Fix First"
description: "Salesforce Health Insights addresses enterprise org health monitoring by combining configuration metadata with runtime telemetry to identify and prioritize remediation. The team evolved a static report into an in-app experience with durable finding dispositions, approximately 400+ signals across domains, and standards informed by Well-Architected principles and implementation anti-patterns. A shared harmonization layer reconciles fragmented datasets, connector patterns link runtime activity to metadata components, and the system preserves data origin, freshness, and access requirements while keeping deterministic findings distinct from externally supplied context. Prioritization combines findings with request volume, application and database CPU, call behavior, and peak-business-hour traffic to rank next best actions by criticality and effort. A headless JSON schema supports interfaces including an MCP connection, while the deterministic core is intended to produce dependable recommendations and extend access beyond the primary interface."
---

# How Metadata and Runtime Telemetry Reveal Which Enterprise System Problems to Fix First

[Salesforce](https://yomu.fyi/company/salesforce) · Scott Nyberg · Sep 8, 2026

**Type:** Explainer

## Summary

Salesforce Health Insights addresses enterprise org health monitoring by combining configuration metadata with runtime telemetry to identify and prioritize remediation. The team evolved a static report into an in-app experience with durable finding dispositions, approximately 400+ signals across domains, and standards informed by Well-Architected principles and implementation anti-patterns. A shared harmonization layer reconciles fragmented datasets, connector patterns link runtime activity to metadata components, and the system preserves data origin, freshness, and access requirements while keeping deterministic findings distinct from externally supplied context. Prioritization combines findings with request volume, application and database CPU, call behavior, and peak-business-hour traffic to rank next best actions by criticality and effort. A headless JSON schema supports interfaces including an MCP connection, while the deterministic core is intended to produce dependable recommendations and extend access beyond the primary interface.

## Context

Enterprise Salesforce implementations accumulate products, customizations, integrations, automation, and technical debt while telemetry remains scattered across tools with different identities, freshness levels, and access rules. Without a shared definition of implementation health and a way to rank findings, customers can face decision paralysis and lack clarity about what to fix first.

## Approach / What changed

The team created an in-app schema for findings and durable dispositions, expanded health signals across security, process automation, agentic readiness, customization, and data model domains, and added a shared harmonization layer with connectors linking runtime telemetry to metadata. It combines deterministic configuration findings with operational context, ranks remediation by criticality and effort, and exposes raw JSON through headless interfaces including MCP.

## Takeaways

- A shared harmonization layer connects fragmented metadata and runtime telemetry while preserving each dataset’s origin, freshness, and access requirements.
- Prioritization uses request volume, application CPU, database CPU, call behavior, and peak-business-hour traffic alongside metadata findings.
- The headless architecture emits raw JSON for UIs and agents, and an MCP interface can provide guidance on security, implementation patterns, and anti-patterns.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [Data Governance](https://yomu.fyi/topic/data-governance), [MCP](https://yomu.fyi/topic/mcp), [Observability](https://yomu.fyi/topic/observability)

- Source: [Salesforce](https://engineering.salesforce.com/how-metadata-and-runtime-telemetry-reveal-which-enterprise-system-problems-to-fix-first)
- Source URL: https://engineering.salesforce.com/how-metadata-and-runtime-telemetry-reveal-which-enterprise-system-problems-to-fix-first
- Ingested by Yomu: 2026-09-09T00:00:50.366Z

[Read original post](https://engineering.salesforce.com/how-metadata-and-runtime-telemetry-reveal-which-enterprise-system-problems-to-fix-first)