Debugging On-Prem PMS with RPCs
Why This Matters
When an on-prem SyncApp is misbehaving, you can't just look at Kubernetes logs — you need to call into the running process using RPC commands. Knowing which RPC commands exist and how to use them is an essential on-prem debugging skill.
What You'll Learn
- What RPC (Remote Procedure Call) commands are in the context of SyncApp debugging
- How to use the Useful RPC Commands reference document
- When to use RPCs vs WAM logs for on-prem debugging
- Common debugging scenarios that require RPC access
Watch Video
Open in Google Drive
💡 Open in Drive for AI-powered transcript search and summaries
Lesson Summary
On-prem SyncApps expose RPC endpoints that let developers inspect the running process, trigger manual syncs, check sync status, and debug data issues. The Useful RPC Commands document (linked in resources) contains the full list of available commands. Unlike cloud SyncApps where WAM provides visibility, on-prem debugging often requires direct RPC interaction with the process running on the customer's VM.
Key Concepts
RPC CommandsOn-Prem DebuggingSyncApp Process InspectionManual Sync Trigger via RPCWAM vs RPC Debugging
Key Takeaways
01Bookmark the Useful RPC Commands document — you'll reference it for every on-prem debugging session
02RPCs let you inspect a running SyncApp without restarting it or touching the customer's machine configuration
03Use RPC commands when WAM logs aren't giving you enough detail on an on-prem sync issue
04RPCs can trigger manual syncs for specific entities — useful for targeted debugging without waiting for the full cycle