Results 1 to 2 of 2

Thread: Discovery of servers in scaling group

  1. #1
    Junior Member
    Join Date
    Apr 2016
    Posts
    2

    Exclamation Discovery of servers in scaling group

    Cloud providers (Azure, AWS) let you set up many servers in a scaling group, but most of the servers will not be turned on until they are needed. They will be turned on and off based on server load. This leads to scenarios where (for example) 3 of 7 servers are intentionally turned off, as they are not needed. In this case, I do not want Shinken to tell me that the servers are turned off, because I want them to be turned off if they are not needed.

    However, if a server is turned on when the service gets busy, I now want Shinken to tell me if that server is not working like it should.

    Can the discovery module work with these kinds of situations?

    If not, does anyone have any recommendations on how to approach solving this problem?

  2. #2
    Self-discovery is launched for all people. The themes of the edubirdie review are applied to humans. The essence is counted for the fulfillment of goals. The movement is filed for the approval of the terms for the senior items. The movement is filled for humans.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •