Yes, when we make a change which affects a group we generally want every group (and checker) which references the group, even indirectly, to get updated. And they need to get updated in the correct sequence with referencing groups getting updated after the groups they reference (assuming no circular references). Our approach for when we wanted to be sure everything was updated was to rebuild all of the groups about six times since we didn't see any guarantee on the sequence of the updates.
We'll wait for the discovery script changes to make it to a stable version. Using the script works for those who can ssh into the Observium host but is definitely less convenient than a button in the GUI. Is there any harm caused by extra rebuilds of the groups or checkers? Corwin On Wed, Jul 31, 2024 at 7:51 PM Adam Armstrong via observium < observium@lists.observium.org> wrote: > Hi, > > It's not really necessary anymore. We removed the button because people > kept saying they were clicking it when it's not really necessary. > > Though I suppose in this instance, it's because you want to trigger an > update of groups that other than the one you've changed? > > You can actually force a full rebuild with "./discover.php -a" (I just had > to commit a fix to this, so you need the latest version for this to > actually work). > > I might look at putting it back in the UI somewhere, but that button used > to cause some confusion, so I probably won't put the button back. > > Thanks, > adam. > > Corwin Ziegler Hunts via observium wrote on 2024-07-29 20:54: > > Hi, > > We use Observium groups extensively, often nested several times. Our alert > checkers then reference these groups. After making changes to a group, > including by adding a device, we used to force rebuilds of the groups > (possibly several times) and checkers so the changes would propagate all > the way through. We are on the latest stable revision (r13582) and the > rebuild buttons are no longer available in the UI (possibly removed in > r13391). What should we do now when we need to forcibly propagate changes? > > Corwin > > > _______________________________________________ > observium mailing list -- observium@lists.observium.org > To unsubscribe send an email to observium-le...@lists.observium.org > > > _______________________________________________ > observium mailing list -- observium@lists.observium.org > To unsubscribe send an email to observium-le...@lists.observium.org >
_______________________________________________ observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-le...@lists.observium.org
