DevOps & Infrastructure
Agentforce Observe
Analyze production Agentforce agent behavior using session traces and Data Cloud, and manage Agent Health Monitoring (AHM) alerts. TRIGGER when: user queries STDM session data or Data Cloud trace records; investigates production agent failures, regressions, or performance issues; asks about session traces, conversation logs, or agent metrics; wants to reproduce a reported production issue in preview; runs findSessions or trace analysis queries; creates, lists, updates, or deletes an AHM data alert on an agent metric (escalation rate, deflection, etc.); asks why an alert is not firing or wants to check whether alerts have fired (notification counts, or the per-alert Incidents view). DO NOT TRIGGER when: user creates, modifies, or debugs .agent files during development (use agentforce-generate); writes or runs test specs (use agentforce-test); uses sf agent preview for local development iteration; deploys or publishes agents.
- Publisher / source
- forcedotcom/sf-skills (found on skills.sh)
- Upstream record
- forcedotcom/sf-skills
- Version
- Version 3
- Published
- Publication review
- Approved for publication · recorded passed scan 2026-11-02
- Content fingerprint
9c9f626f0d23d253581f706df585cfe3d6eab021dde5c2b03b91404f8f0557e9