MasterTest swap to GOOD->Retest all "Waiting for Mas
MasterTest swap to GOOD->Retest all "Waiting for Mas
Dear Alex,
when a Master Test is in BAD status, after a while all the depended tests will change to "Wait for Master"
I'd like to have the following:
When a Master Test changes back to GOOD, then retest all of the depended tests (at least those that are "Waiting for Master") immediately to get an up to date status of the network as soon as possible.
Many thanks
Juergen
EDIT:
Could be a new Action (for GOOD ActionProfile):
- Retest all "Waiting for Master" dependent tests
- Retest all dependent tests
when a Master Test is in BAD status, after a while all the depended tests will change to "Wait for Master"
I'd like to have the following:
When a Master Test changes back to GOOD, then retest all of the depended tests (at least those that are "Waiting for Master") immediately to get an up to date status of the network as soon as possible.
Many thanks
Juergen
EDIT:
Could be a new Action (for GOOD ActionProfile):
- Retest all "Waiting for Master" dependent tests
- Retest all dependent tests
Last edited by JuergenF on Sun Dec 24, 2006 6:23 am, edited 3 times in total.
-
- Posts: 229
- Joined: Tue Jun 20, 2006 1:20 pm
- Location: Montreal, Quebec
-
- Posts: 229
- Joined: Tue Jun 20, 2006 1:20 pm
- Location: Montreal, Quebec
At the moment, I created a view with all «not good» tests and I have to manually log in and select the view + force a manual refresh on these «slave» tests.
[Auto refresh tests when MASTER TEST returns to GOOD] option could be implemented and is important and needed.
When all lines are yellow and red on monitoring screens, we have to take action and all attention gets toward the problem... So, if tests re-check automatically, alerts would last less longer and people would be updated more quickly.
Also, even when the master test is back to good, the slave tests still displaying «waiting for master» are announcing a «not perfectly good» situation.
Please don't forget to implement an option like this, preferable in the «options / Behavior» window.
- An extra button to the right of the actual «Refresh» on the RCC GUI called lets say «Refresh Slave Tests» would also be appreciated.
- An action like JuergenF said, that would fire the «Refresh Slave Tests» would also be appreciated.
[Auto refresh tests when MASTER TEST returns to GOOD] option could be implemented and is important and needed.
When all lines are yellow and red on monitoring screens, we have to take action and all attention gets toward the problem... So, if tests re-check automatically, alerts would last less longer and people would be updated more quickly.
Also, even when the master test is back to good, the slave tests still displaying «waiting for master» are announcing a «not perfectly good» situation.
Please don't forget to implement an option like this, preferable in the «options / Behavior» window.
- An extra button to the right of the actual «Refresh» on the RCC GUI called lets say «Refresh Slave Tests» would also be appreciated.
- An action like JuergenF said, that would fire the «Refresh Slave Tests» would also be appreciated.
-
- Posts: 229
- Joined: Tue Jun 20, 2006 1:20 pm
- Location: Montreal, Quebec