Results 1 to 4 of 4

Thread: how often, triggered by what?

  1. #1

    how often, triggered by what?


    how often is a discovery meant to be run? Once at installation time? No. If your boss says "we have new hosts/services"? No. If your colleague tells you that he has migrated some virtual machine to another hypervisor? Can you elaborate a little more? I think I didn't get the whole picture of the discovery process.


  2. #2
    Shinken project leader
    Join Date
    May 2011
    Bordeaux (France)

    Re: how often, triggered by what?

    The discovery can be done as soon as you want, like update your data or add a new host for a specific new host scan ;D
    No direct support by personal message. Please open a thread so everyone can see the solution

  3. #3

    Re: how often, triggered by what?

    I think I just have to try this out and see what happens.


  4. #4
    Join Date
    Dec 2011

    Re: how often, triggered by what?

    The only caveat is updating the configuration too often can impact acquisition and the frontend depending on how many services you are running.

    For example with installations with more than 10K services.

    Care also needs to be taken when updating the configuration to be able to back-out a change. Use subversion or other change control system to keep a history. This way you do not cause unplanned outages looking for a piece of borked configuration that is causing Shinken to bail.



Posting Permissions

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