Monitoring

The French text governs. This page is the English version of Supervision FR.

34 capabilities answering a single question: is your org standing up right now, and since when? What the Discovery offer opens among them, at zero euros, with no Shield and not a single outbound call: 10.

34

capabilities in this family

10

active on installation day, on the Discovery offer

Discovery

entry tier of the family

What this family measures

OrgGuardian's monitoring reads what the platform already exposes to an administrator and turns it into a series: platform limits and their consumption, org health score, failed logins, depth and failures of the asynchronous queues, API versions of components, and the inventory of the endpoints your org calls outside.

Every measurement carries a stable key, the one you will find again in the API and in the export: Org:HealthScore, Monitoring:FailedLogins, Monitoring:AsyncQueueDepth, Monitoring:UnhandledExceptions, Callouts:PostureScore. A key does not change meaning between two versions: that is what makes the series comparable over time, and that is the whole point of monitoring as opposed to a screenshot.

The fourth block of the table below no longer observes the org: it observes the measurements already taken. Intra-org baseline, seasonality by hour band and weekday, correlation between findings, cohort benchmark. That is where the product stops saying “here is the value” and starts saying “here is the value, and it is abnormal for a Tuesday morning”.

The 34 capabilities, one by one

— display tier: nothing to toggle, the offer is enough

Source: read from the package code at the moment this page is built — FeatureGate.FEATURE_TIER for the offer, FeatureGate.CODE_DEFAULTS for the state at install. The label is the one exception: the in-org feature editor is French only, so the English wording in this column was written for this site. Its French counterpart, on /produit/, is the exact string your administrator reads, and the site build fails if the two lists move apart. “Closed” does not mean absent: the capability is shipped, it is waiting for a human to open it inside the org — and a capability whose implementation nothing in the package can reach appears on none of these pages: the build drops it instead of selling it.

What this family does not do

• It fixes nothing. No capability on this page writes into your configuration: the product detects and advises, a human decides.
• It is not real time. The freshness of a measurement is that of the last scan, not of a continuous stream; a capability that could not measure says so in a finding instead of showing an old number.
• The four Event Monitoring detectors need a Shield licence on the Salesforce side. Without it they stay silent — and the Monitoring_EmProbe probe tells you precisely whether your org has one.
• It does not monitor your third-party systems. It measures what your org does towards them (calls, failures, endpoints), not what happens on their side.