Hi Robert. I’ll add a couple more things that I know to Giri’s answer. If using SEMPv2, which can monitor any VPN-level object, you can find all the documentation, paths, and descriptions here: SEMP API Reference (followed from the “Monitor” link on this page: SEMP API Reference ).
SEMPv2 still doesn’t cover that many broker/system level commands. For that you’ll have to use SEMPv1, and older XML-formatted API. Unfortunately there isn’t really any documentation for the schema, you have to kind of “know what you’re looking for”. There’s a page here about SEMPv1: Legacy SEMP
Luckily if you know the CLI command you’re trying to do (e.g. show stats client for broker-level message rate stats), there is a useful command-line utility built into the broker which can convert from CLI to SEMPv1. If you login to the support shell (on Docker: docker exec -it containerName bash , or enable → shell support on appliances), then you can run cli-to-semp and then type in the CLI command.
Also, I made this big list of things you can poll with SEMPv1 a long time ago as part of a utility that I wrote, and the XML request payload you need to pass as part of the POST command, maybe it will help: Aaron's StatsPump Poller documentation Ignore the “poller” stuff, just notice the SEMP commands, and look at the “SempXmlFactory Message” payload response to see what the response can look like. Also, in the POST request body, you don’t need to specify the semp-version in the header anymore.
In terms of getting the details of RDP response errors (4xx and 5xx), there is a broker-level in-memory log you can query with CLI: show log rest rest-delivery-point errors wide and an equivalent SEMPv1 command. Unfortunately, this isn’t available yet in SEMPv2, and also not exposed in the PubSub+ Manager or Solace Cloud Console, so I made a little utility to help pull these logs out: RDP Error Log Viewer
Hope that helps!