I have recently tired to find how to enhance my system administration career .. As it is true every time, To get enhanced, I have to get my abstraction level higher ..this is when IT service management has took my notice..
I am not a ITIL expert.. In fact a baby on that field.. In this field I have studied bussiness process Add ON. and I can share my insights with you.. >I think the requirements you are asking for is: >* an overall view of a business service, with a health indication >based on some complex logic to determine the "actual" state Put the IT componenets, which business service depends on, side by side . If when that component fails, the bussiness service fails then put an AND operation after that component. When occurs, Mark business service as CRITICAL If when that component fails, the bussiness service DOES NOT fail then put an OR operation after that component. When occurs, Mark business service as DEGRADED >* a click on this business service to then show the state of the >clusters involved in this business service (web servers, app servers, >db servers, 3rd party) >* a click on the clusters (or all) to see all the components >(individual services) > * (I assume 3 levels of hierarchy is sufficient at the moment) >* maybe in addition, a top level view of all "business services" 2 levels are enough for now.. Business service and when clicked on it, all the depended IT components.. >So this would satisfy your customers (who care about the top level >state of the business service), and satisfy your technical support >staff (who want to see the state of all the components comprising of >the business service and not other unrelated "things"). >Is that right? YES! >Assuming this is correct, how would you configure this? I can see >you'd need to find: >* a way of grouping the services together (component level) This has already done bu Business Process Addon, you can simply integrate it.. If you want to rewrite, I have explained it above.. >* a way of representing the summarised component level (perhaps >some logic about clustering) >* a way of grouping these summarised components together (cluster >level) No need for those levels for now! >* a name for these summarised components (business level) >Where and how would you add these into the current Opsview interface? Under status (better) or modules (if you integrate) >What changes are required at the Nagios level? In fact this is a very hard question. I am repeating the ideas of David Josephsen (from Building a monitoring infrastructure with nagios book) The Down Side of Hosts and Services In my opinion, the manner in which Nagios naturally handles the host and services paradigm is genius. It is simple to understand, always does what you would expect, and makes things generally easy to manage. However, the hosts and services assumption also limits Nagios’ functionality, to some degree. To understand why, consider a large corporate or university email system. Such a system is composed of MXs and border mail systems, internal relay servers, and user-facing group- ware. Outages of various services and hosts within the email system affect the entity as a whole but don’t necessarily make it completely unavailable. An MX outage (can be multiple MXs), for example, might do nothing at all to affect the fl ow of mail, whereas a groupware outage might mean that mail is still being delivered to the MXs, but that users cannot interact with it. Business processes and higher-level entities, such as email, are diffi cult to capture on a host and service scale, because they are actually an aggregation of many services on many hosts. Nagios provides host and service groups, which can contain individual services from different hosts. So a service group called email can be created, which would summarize the status of each service that corporate email depends upon. But given that post offi ce protocol (POP) on Server1 is unavailable, it is not obvious what effect this outage has on the overall email entity to the uninitiated. Given that Nagios plugins are user-defined, and in many cases, user-created, an enterpris- ing admin could write a single plugin to check the overall status of the email system piece by piece. But within the hosts and services paradigm, to which host would the service that plugin checks belong? >What kind ofauthorisation would be needed for the components, cluster and >business level views? We can add a new auth role..because this view will be expected by management level.. >How do you report on these? Would this work in a distributed environment? You mean notifications ? This should be, but not a must. I cant figure out now. May be this can be postponed to version 2 ;) This will work in in Distr env. because components can be unrelated. You just put AND/OR logic to get a result! >(BTW, those are questions I have to answer for every new piece of >functionality!) >Ton “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
