Retrieve Apache Pulsar function statistics with pulsar-admin

domain: pulsar.apache.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Ensure your Pulsar function is deployed and running — verify with: pulsar-admin functions status --name {function-name} --namespace {tenant}/{namespace}
  2. Retrieve aggregated function statistics using: pulsar-admin functions stats --name {function-name} --namespace {tenant}/{namespace} --tenant {tenant}
  3. The stats output includes: receivedTotal, processedSuccessfullyTotal, systemExceptionsTotal, userExceptionsTotal, avgProcessLatencyMs, lastInvocationTime, and per-instance breakdowns.
  4. For per-instance statistics (useful when parallelism > 1), add --instance-id {id} to the stats command to scope to a single function instance.
  5. To monitor stats continuously, combine with a polling loop or configure Pulsar's built-in Prometheus metrics endpoint on the function worker.

Known gotchas

Related routes

Set up Apache Pulsar Functions to perform stateless stream processing and deploy via pulsar-admin
pulsar.apache.org · 5 steps · unrated
Create and update a Pulsar IO source connector via pulsar-admin
pulsar.apache.org · 5 steps · unrated
Configure Apache Pulsar namespace-level message encryption with end-to-end encryption
pulsar.apache.org · 5 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans