Hi,
Having followed this thread from the side - since we are in the same
dilemma.
Our business (trading) does not allow for complex systems. to show where
in the business process an item has failed. By nature, traders are very
prompt in noticing problems :) It is a like a game where we want to be
them notifying we have a problem, instead of them notifying us.
We have attempted to setup a BI monitoring process. By defining the
services involved (step1) then defining what the effect would be if a
service goes to warning and what the effect would be if a service would
be critical (step2). The result was a tree - based on the location in
the tree, the BI process would be green, yellow or red. This was fed
from opsview with a global event handler, transferred to mssql to the
machine running tree. (step3). Users were presented a view similar to
the viewports (:P)
Not only was this a slow process - after Opsview noted a problem, the
other system reported similar - the costs for such a system - manpower,
machines and licenses - were far too high.
Therefore we stayed with the viewports, for them seeing the BI process
is green is enough. If any other color they just want to know what's
causing this and when fixed, they don't want to take the time to click
through. SLA availability is reported by Opsview - on request, so
always available. Setting the SLA's corrct also means support staff
needs to be instructed to use the 'sleeping' function of a service if
this is down for maintenance. f..e.
My 0.02$
Paul
M. selcuk karaca wrote:
Hi Ton,
Thanks for your insights.. I recognize your tremendous experience and
knowledge..
What we know makes our world rich but also it puts limits in our minds..
I know End-to-End (E2E) testing is invaluable.. You can easily see bussiness
side and get SLAs..
But there is 1 drawback:
They can only inform that service is unavailable or slow. But does not
reveal which component is causing this.. !
With service tree this is a child game.
This can be understood as a small thing (although not!) but it reflects a
major paradigm shift. You arrange your system componenets according to
customer view.. This also must be placed in nagios core.. As a core nagios
developer you may be interested with this ;)
“This Message (including any attachments) contains confidential information and
is intended only for the individual named. If you are not the named adressee or
not related with the content of this Message, you are forbidden to read,
disseminate, distribute, copy, reproduce or modify this mail by our Company.
Please notfy the sender immediately if you have received this e-mail by mistake
and delete this e-mail from your system. E-mail transmisson can not be
guaranteed to be secure or error-free as the mail may arrive late or incomplete
or the information could be intercepted, corrupted, lost, destroyed, amended, ,
or contain viruses. The sender therefore does not accept liability for any
errors, loss of integrity or confidentiality or ommissions in the contents of
this Message or for the information transmission, reception, storage of use of
such in any way whatsoever, which arise as a result of e-mail transmission. Any
opinions expressed in this message are those of the author and may not
necessarily reflect the opinions of Our Company.
Copyright in documents created by or on behalf of our Company remains vested
in us, and we assert all of our moral and intellectual property rights.”
“Bu mesaj (ve ekleri) gizli bilgi içermektedir ve sadece gönderilen kişiye
yöneliktir. Bu e-mailin muhatabı değilseniz veya içeriği ile ilginiz yoksa,
Şirketimizin onayı olmaksızın bu mesajın okunması, değiştirilmesi,
kopyalanması, üçüncü kişilere açıklanması, yayınlanması, ifşa edilmesi veya
iletilmesi yasaktır. Bu mesajın gönderilmek istendiği kişi değilseniz (ya da bu
e-posta'yı yanlışlıkla aldıysanız), lütfen yollayan kişiyi hemen haberdar
ediniz ve mesajı sisteminizden derhal siliniz. E-mail iletiminin güvenli veya
hatasız olduğunun garantisi olmadığından geç veya eksik iletim veya içerik ve
bilgilerde eksiklik, kayıp, değişiklik veya virüs olabilir. Bu nedenle, bu
mesajın iletiminden dolayı, gönderen, içerikteki hata, eksiklik, doğruluğun ve
gizliliğin ihlalinden veya bu yolla bilgi paylaşımı, iletimi, depolanması gibi
herhangi bir kullanımından hiçbir şekilde sorumlu değildir. Bu mesajın içeriği
yazarına ait olup, Şirketimizin görüşlerini içermeyebilir.
Bu mesajın içeriğinde geçen Şirketimizin ad veya nanıma yaratılan fikri ve
sınai haklar Şirketimize ait olup, maddi ve manevi tüm hakları Şirketimizde
saklıdır.”
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
