• Like
Zenoss presentation (nur nabilah hassan)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Zenoss presentation (nur nabilah hassan)

  • 523 views
Published

first presentation during Industrial Training at Ipeninsula Sdn.Bhd i-City, Shah Alam..

first presentation during Industrial Training at Ipeninsula Sdn.Bhd i-City, Shah Alam..

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
523
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
24
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. PREPARED BY : NUR NABILAH HASSAN
  • 2. ABOUT ZENOSS CORE … • Zenoss (Zenoss Core) is a free and open-source application, server, and network management platform based on the Zope application server. • Released under the GNU General Public License (GPL) version 2. • Provides a web interface that allows system administrators to monitor availability, inventory/configuration, performance, and events. * Zope Application server: An object-oriented web server written in Python.
  • 3. ZENOSS CORE PROVIDES : • Monitoring availability of network devices using SNMP, SSH, WMI • Monitoring of network services (HTTP, POP3, NNTP, SNMP, FTP) • Monitoring of host resources (processor, disk usage) on most network operating systems. • Time-series performance monitoring of devices
  • 4. ZENOSS MAJOR PARTS : • User Layer (Web Portal) • Watch the status of your enterprise, using the Dashboard • Work with devices, networks, and systems • Monitor and respond to events • Manage users • Create and run reports *The user layer Interacts with the data layer and translates the information for display in the user interface.
  • 5. ZENOSS MAJOR PARTS : • Data Layer • Configuration and collection information is stored in the data layer, in three separate databases: • ZenRRD- Utilizing RRDtool, stores time-series performance data. Because RRD files are stored locally to each collector, no bottlenecks result from writing to a single database as new collectors are added. • ZenModel- Serves as the core configuration model, which comprises devices, their components, groups, and locations. It holds device data in the ZEO back-end object database. • ZenEvents- Stores event data in a MySQL database
  • 6. • Process Layer • manages communications between the collection and data layers • utilizes Twisted PB (a bidirectional RPC system) for communications. • Collection Layer • comprises services that collect and feed data to the data layer • Provided numerous daemons that perform modeling, monitoring, and event management functions.
  • 7. ADVANTAGES : • Open Source • Free and open source • Backed by the efforts of a large community of users • Deploy and adapt on your own terms • Full Lifecycle Visibility • Monitor performance and availability • Centralize fault/alarm/event management • Real-time alerting & reporting • Physical and Virtual IT Infrastructure • Single integrated view of networks, servers and apps • Seem less visibility between virtual and physical machines • Cross-vendor, cross-platform support (Windows, Linux, Unix)
  • 8. • Scalable for the Enterprise • Auto-discovery and policy-driven configuration makes it easy to configure in large environments • Management tools for large, distributed configurations • High availability • Open, Flexible Architecture • Open architecture makes it easy to customize and extend • Open standards and agentless deployment eliminate lock-in • Affordable • Use what you like for free
  • 9. ANNOYANCES : • Web interface feels slow (Zope is bloated) • Limited open-source version. Full version needs to be paid for. • Performance • SELECT operation in MYSQL Database produces extra high I/O when getting some data from the Events History. • Complexity • requires a bit more than a superficial knowledge of the interface • Opaque operation • You can add monitoring and check back later if anything worked they way you want.
  • 10. • Configuration and data is spread across MySQL, the internal Zope database storage and RRD files on disk.