Ensure your Pulsar function is deployed and running — verify with: pulsar-admin functions status --name {function-name} --namespace {tenant}/{namespace}
The stats output includes: receivedTotal, processedSuccessfullyTotal, systemExceptionsTotal, userExceptionsTotal, avgProcessLatencyMs, lastInvocationTime, and per-instance breakdowns.
For per-instance statistics (useful when parallelism > 1), add --instance-id {id} to the stats command to scope to a single function instance.
To monitor stats continuously, combine with a polling loop or configure Pulsar's built-in Prometheus metrics endpoint on the function worker.
Known gotchas
The correct subcommand is pulsar-admin functions stats — the subcommand get-stats does not exist in the Pulsar admin CLI and will return an error.
Stats are reset when a function is restarted or redeployed; do not rely on receivedTotal for long-term accounting across deployments without an external metrics store.
The --namespace flag expects the full tenant/namespace path (e.g., public/default), not just the namespace portion alone.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp