---

Subject:	Systems are made up of
Author:	Andrew Kirch
Posted:	2016-03-30 15:00

Systems are made up of various compoents which Zenoss can autodetect. For instance in a 24 port switch, if you model the switch, it'll find all 24 ports.
If you model a linux server, it'll find the cpu's, ram, storage, ethernet interfaces, running services, etc.
the model is dynamic and updated every 24 hours.
So in essence, modeling is how Zenoss ensures that it knows as much about eachsystem as possible, and if something changes, you often don't have to tell Zenoss about the change.

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard

---

Subject:	Wow - that's great!
Author:	Larry Virden
Posted:	2016-03-31 05:02

That is a wonderful description of the function. I wondered if that might be a part of it.

So it is basically gathering just the hardware information about the device.

So much to learn. I wish there were good tutorials to walk us through this process.

---

Subject:	Lvirden,
Author:	[Not Specified]
Posted:	2016-04-21 02:48

Lvirden,

It can be more than that. Modeling collects information which one would only need to occasionally poll or probe for, usually about every 12 hours. An example would be the number and details on interfaces, the number and details on filesystems, the total amount of device memory, the number of processes matching a regex running and so on. Most data collected during modeling is not graphed. This is in contrast to the performance data items (datasources and datapoints) collected in templates. These are items that are typically graphedand polled every 1 to 5 minutes.

ZenMaster Shane William Scott (Hackman238)

CTO

GoVanguard Inc.

sscott@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard