Jump to content

Jeremy

Members
  • Content Count

    3
  • Joined

  • Last visited

About Jeremy

  • Rank
    IT Apprentice

Profile Information

  • Location
    Lynnwood, WA
  1. This is awesome. This is likely to be an interim plan for me while I write something more custom tailored for me. I would suggest you return a unique value for maintenance mode, rather than the same as a failure to run. The reason for this is many people will need to error on a failed polling the same as if the script returned bad stuff, but we would not want to do the same if its in maintenance mode. Looking at the code it doesn't look to hard to change since you already checking separately, but if i'm understanding the code correctly you would only need to return somethin
  2. 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: se
  3. This may not be an Rest API thing, but in reading the documentation, it sounds like it MAY be. I have a distributed, multi-system, multi-service application, of which I want to monitor the status via running an RPC status binary I have which outputs XML containing a system, service, and status. Some assumptions I'd like confirmed System Publish can be used to publish custom status More than one system could publish into the same instance (assuming they don't run at the same time) Rest API is a good way to do this (there isn't a better way) If this is a bad cho
×
×
  • Create New...