Understood. I'm looking deeper into the links provided.
Those didn't seem ideal, as the client seems tied to a single host and I wanted to instead monitor the environment with redundancy. It seems pulseway lacks any good way to do many-to-one relationships, such as what you might see with clustering or VIPs.
Out of curiosity, where does a developer go to learn how to then use this system publish? (Does the regular client not publish on its own? aka this is for essentially custom)
Let me give you an idea of what i'm looking for
system1: service1, service2
system2: service3, service4
For example. And my RPC will connect to an RPC service on either system1 or system2, and return status for all 4 services. If I report per-system, i'll need to parse the output down to only the services installed on that system, and it will require me to have the RPC component installed on all systems which have application services. This means if the local RPC fails, status for components locally cannot be polled (and thus fail) and if I want to status the environment I have to group systems within pulseway.
Alternatively I could forgot monitoring redundancy and just pick one system to monitor the entire environment, but this is inferior to the custom monitoring and alerting I already do which I was trying to get Pulseway to replace.
I was thinking the Rest API would be the way, but the documentation doesn't seem to indicate how to publish monitoring data. In what case would it be useful to "Publish a system" without ever publishing monitoring data? (again, I believe the client will automatically publish it-self if configured correctly)