Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Zenoss Core 3.x Network and System Monitoring

You're reading from   Zenoss Core 3.x Network and System Monitoring A step-by-step guide to configuring, using, and adapting this free Open Source network monitoring system

Arrow left icon
Product type Paperback
Published in Apr 2011
Publisher Packt
ISBN-13 9781849511582
Length 312 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Michael Badger Michael Badger
Author Profile Icon Michael Badger
Michael Badger
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Zenoss Core 3.x Network and System Monitoring
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Network and System Monitoring with Zenoss Core 2. Discovering Devices FREE CHAPTER 3. Device Setup and Administration 4. Monitor Status and Performance 5. Custom Monitoring Templates 6. Core Event Management 7. Collecting Events 8. Settings and Administration 9. Extending Zenoss Core with ZenPacks 10. Reviewing Built-in Reports 11. Writing Custom Device Reports Event Attributes
Device Attributes
Example snmpd.conf
Index

Command line discovery with zendisc


The zendisc daemon gives us an opportunity to discover devices from the command line. It can be a helpful troubleshooting tool, or it can be a way for you to shed the Web interface and satisfy your curiosity about how Zenoss Core works. Let's take a look at a few example commands.

To see a list of available options, run the following command as the zenoss user:

zendisc help

Let's work through an example where we remodel a device on our network. Modeling the device gives Zenoss Core the characteristics about the device that we monitor. Sometimes Zenoss Core may not be collecting the information we think it should, so we need to figure out why.

Run the following command as the zenoss user:

zendisc run --remodel -d coyote --logseverity=10

Because we used the --logseverity=10 option, the output is verbose and we can step through the remodeling process, one line at a time. A value of 10 provides the highest level of verbosity.

The -d coyote option ran the --remodel...

You have been reading a chapter from
Zenoss Core 3.x Network and System Monitoring
Published in: Apr 2011
Publisher: Packt
ISBN-13: 9781849511582
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image