Zenoss开发者指南：企业级管理开源技术

需积分: 10 131 浏览量更新于2024-07-23 收藏 1.45MB PDF 举报

"Zenoss Developers Guide 08-102010-3.0-v01" 是一本由Zenoss, Inc.出版的开发者指南，主要关注Zenoss监控系统的开发与应用。该指南受Creative Commons Attribution Share Alike 3.0 许可证保护，允许在遵循一定条件的情况下自由使用、分发和修改内容。书中涉及了多个知名品牌的商标信息，如Adobe的Flash、Oracle的Java、Linux操作系统、Oracle公司的Oracle品牌、Sybase数据库、Apache Software Foundation的Tomcat以及微软的Windows等。在Zenoss监控系统中，开发者可以了解到如何利用Zenoss进行企业级的IT运维监控。Zenoss是一个开源的企业级监控平台，它集成了网络、服务器、应用程序和存储设备的监控，提供了一个统一的视图来管理IT基础设施。Zenoss的核心特性包括事件管理、性能监控、配置管理、自动发现和报告等。开发者可以通过Zenoss的API、插件机制或自定义脚本来扩展其功能，以适应特定的IT环境需求。在Zenoss Developer's Guide中，可能包含以下关键知识点： 1. **Zenoss架构**：解释Zenoss的组件结构，包括核心服务、数据存储、用户界面以及与被监控设备的交互方式。 2. **ZenPack开发**：ZenPack是Zenoss的扩展机制，开发者可以通过编写ZenPack来添加对新类型设备或应用的监控支持。 3. **REST API**：介绍Zenoss的RESTful API，用于程序化地与Zenoss服务器进行交互，如查询数据、执行操作或自动化任务。 4. **事件处理**：讨论Zenoss如何处理事件，包括事件生成、事件关联、报警策略和通知机制。 5. **性能监控**：讲解如何配置和分析系统性能指标，包括CPU、内存、网络和磁盘I/O等。 6. **配置管理数据库(CMDB)**：介绍Zenoss如何维护CMDB，以及如何通过CMDB进行配置管理和变更跟踪。 7. **自动发现**：阐述Zenoss如何自动发现网络中的新设备和服务，并将其纳入监控范围。 8. **集成其他技术**：可能会提到如何将Zenoss与其他系统集成，如SNMP Informant用于SNMP设备的监控，或者与Java、Tomcat等技术的整合。 9. **故障排查和调试**：指导开发者如何诊断和解决Zenoss系统的问题，包括日志分析和问题定位技巧。 10. **安全性和权限管理**：涵盖Zenoss的安全设置，用户和组的权限控制，以及数据的保护措施。该指南对想要深入理解Zenoss监控系统、开发自定义解决方案或者优化现有监控部署的开发者来说，是一份非常有价值的参考资料。通过学习和实践，开发者可以有效地提升Zenoss在企业IT环境中的效能和适用性。

Getting Started

@rtype Data type of the return value

@permission Zope permission that the method requires

@todo Todo for this method

Note

Within the description section of the docstring, you may use the string DEPRECATED on its own line to denote that

the method is deprecated.

2.1.5. Generating Diffs for new Fixes

Once you have determined how to fix something, or have found a way to add a feature, modify the source code in

your checkout directory. Once that is complete, generate a diff starting from the base of the checkout directory.

To generate a diff of all files in the current directory and all subdirectories:

$ svn diff > mychanges.diff

To produce a diff for just a single file:

$ svn diff source_file > mychanges.diff

2.1.6. Submitting a Fix

Zenoss accepts user contributions using the following procedure:

1. Complete the form to allow Zenoss to accept your code.

2. Create a ticket in our ticketing system.

3. Add the keyword contribute to the ticket.

4. Attach your patch (in diff format) or code to the ticket.

Note

All contributions will be accepted under the terms of the Zenoss Contribution Agreement.

2.2. Development Toolchain Requirements

There are a number of other tools that are required to build Zenoss from source (a toolchain). Among them are a

C compiler, the make command, and other associated tools.

2.2.1. Appliance

The Zenoss appliance is based on the rPath Linux 1 (rp11) distribution.

Troves (like the gcc toolchain) that are not available on the Zenoss update repository server are generally available

from install labels, such as:

conary.rpath.com@rpl:1

The trove candy store is rBuilder Online. Zenoss recommends that you obtain an account there. It provides good

search capabilities for packages of interest, and offers forums to assist with appliance-specific questions.

For a gcc toolchain, try this as the root user:

# conary update --resolve autoconf automake make which \

Getting Started

--install-label="conary.rpath.com@rpl:1"

# conary update --resolve gcc=conary.rpath.com@rpl:1 \

--install-label="conary.rpath.com@rpl:devel"

The binutils trove should already be on the box.

An actual install sequence looked like the ouput below. If the --info switch is used, it is possible to see if everything

is going to resolve nicely. And if you are really paranoid, use the --test flag which runs through the update but does

not commit the result.

# conary update autoconf automake make which --resolve --info \

--install-label="conary.rpath.com@rpl:1"

Install autoconf(:data :doc :runtime)=2.59-7-0.1

Install automake(:data :doc :runtime)=1.9.6-3-0.1

Install m4(:runtime)=1.4.3-4-0.1

Install make(:doc :locale :runtime)=3.80-7.2-1

Install which(:doc :runtime)=2.16-3-0.1

# conary update autoconf automake make which --resolve \

--install-label="conary.rpath.com@rpl:1"

Including extra troves to resolve dependencies:

m4:runtime=1.4.3-4-0.1

Applying update job:

Install autoconf(:data :doc :runtime)=2.59-7-0.1

Install automake(:data :doc :runtime)=1.9.6-3-0.1

Install m4(:runtime)=1.4.3-4-0.1

Install make(:doc :locale :runtime)=3.80-7.2-1

Install which(:doc :runtime)=2.16-3-0.1

# conary update --info --resolve gcc=conary.rpath.com@rpl:1 \

--install-label="conary.rpath.com@rpl:devel"

Install gcc(:devel :devellib :doc :lib :locale :runtime)=3.4.4-9.4-1

Install libgcc(:devellib)=4.1.2-11-1[~!gcc.core]

# conary update --resolve gcc=conary.rpath.com@rpl:1 \

--install-label="conary.rpath.com@rpl:devel"

Including extra troves to resolve dependencies:

libgcc:devellib=4.1.2-11-1

Applying update job:

Install gcc(:devel :devellib :doc :lib :locale :runtime)=3.4.4-9.4-1

Install libgcc(:devellib)=4.1.2-11-1[~!gcc.core]

Generally try to find something on the rpl:1 branch name and do not mix rpl:2 stuff with the rpl:1 stuff. In some

cases, you may have to resort to pulling a trove from the rpl:devel branch if it cannot find it elsewhere. That's what

happened above when trying to resolve the libgcc dependency for the gcc trove. Adding the extra --install-label

option was necessary so that libgcc could be found. How could you know it was on rpl:devel? Go to rBuilder Online

and search for that package and it should tell you.

If you want to see where the files for a trove are installed:

# conary q trove_name --lsl

[code]# conary q gcc --lsl

...

lrwxrwxrwx 1 root root 3 2004-07-07 17:04:44 UTC /usr/bin/cc -> gcc

-rwxr-xr-x 1 root root 81452 2006-06-19 18:02:30 UTC /usr/bin/gcc

-rwxr-xr-x 1 root root 16134 2005-10-15 07:22:42 UTC /usr/bin/gccbug

...

Lastly, conary makes it relatively easy to run-away if you're not happy with a trove you've installed. Use conary

rblist to see what packages have been committed to the conary stack.

# conary rblist | more

Getting Started

http://USERNAME:PASSWORD@MY_ZENOSS_HOST:8080/zport/dmd/

Devices/Server/Linux/devices/angel/getRRDValue?dsname=laLoadInt5_laLoadInt5

Note these things about this URL:

• /zport/dmd/Devices/Server/Linux/devices/angle is the full path to the object you want to access.

• getRRDValue is the method in the Device object you want to run.

• dsname is a parameter to the getRRDValue method.

• laLoadInt5_laLoadInt5 is the value of dsname, which is the name of the data source we are interested in

Watching the URLs as you browse the Web interface can give you a place to start searching.

2.3.1.2. Sending an Event

Events can be sent to Zenoss through the Web interface as well as through using zensendevent, but also through

a programmatic interface.

2.3.1.2.1. Using a REST Call

Sending an event through a rest call can be done by a simple web get. In this example we will use wget to send an

event. If you use wget don't for get to escape the "&" or wrap the URL in single quotes.

[zenos@zenoss $] wget --auth-no-challenge 'http://admin:zenoss@MYHOST:8080/zport/dmd/ZenEventManag-

er/manage_addEvent?

device=MYDEVICE&component=MYCOMPONENT&summary=MYSUMMARY&severity=4&eventclass=EVENTCLASS'

2.3.1.2.2. Using XML-RPC

To send an event to Zenoss using XML-RPC you will first need to create a dictionary (in Perl a hash) that will

represent the event. Zenoss will need at a minimum the following fields:

Event fields

device the name of the device from which this event originates

component the sub-component of the device (for example, eth0 or http)

summary the text message of the event

severity an integer between 0 and 5 with higher numbers being higher severity. Zero is clear.

You can send an event to Zenoss via an interactive session with the Python interpreter as follows:

>>> from xmlrpclib import ServerProxy

>>> myurl= 'http://admin:zenoss@MYHOST:8080/zport/dmd/ZenEventManager'

>>> serv = ServerProxy( myurl )

>>> evt = {'device':'mydevice', 'component':'eth0',

... 'summary':'eth0 is down','severity':4, 'eventClass':'/Net'}

>>> serv.sendEvent(evt)

See below for examples in other languages.

2.3.1.2.3. Example Usage in Other Languages

Please note that we are a Python shop and may not be able to answer specific questions about XML-RPC clients

written in other languages.

2.3.1.2.3.1. Perl

Send an event via Perl using RPC::XML::Client

剩余145页未读，继续阅读

风往北吹哈

粉丝: 30
资源: 10

Zenoss开发者指南：企业级管理开源技术

zenoss_core-4.2.5-2108.el6.x86_64.rpm

zenoss_Developers

zenoss_event_management_exercises_toc

Zenoss_Core_Installation_2.4.0.pdf

Zenoss_Core_Administration 最新版本

Zenoss_Administration Zenoss 管理手册（英文）

zenoss_api:Zenoss JSON API的API连接器

zenoss developer guide

Zenoss Core OVA Installation Guide

zenoss-api

最新资源