1.0

n
Add Threads on page 27
You can increase the number of threads and connections that vCenter Operations Manager generates to
collect metrics from each EMC Smarts adapter instance. Additional threads can improve performance,
but they can also use more domain resources.
n
Configure White and Black Lists on page 28
You can configure the EMC Smarts adapter to use white and black lists to filter resources.
n
Read Events From Notification Lists on page 28
EMC Smarts can store events in notification lists. You can configure the EMC Smarts adapter to read
events from these notification lists and send the events to vCenter Operations Manager.
n
Enable Smart Discovery on page 29
You can configure the EMC Smarts adapter to use smart discovery to discover resources. When you
enable smart discovery, the EMC Smarts adapter performs full discovery during startup and whenever
EMC Smarts reports that it has finished its discovery process.
n
Configure How the Adapter Handles Smarts Processor Metrics on page 30
You can configure how the EMC Smarts adapter handles Smarts processor metrics.
EMC Smarts Adapter Properties File Format
The smarts_adapter.properties file contains properties that affect adapter operation, a series of statements
that define the parts of the EMC Smarts object hierarchy to include in vCenter Operations Manager, and a
series of topo statements that define relationships for container resources.
The following example shows a smarts_adapter.properties file.
ThreadCount=2
AverageProcessors=true
DoSmartDiscovery=false
#classes
# First pair (:: separated)
# 1) where to start (top/bottom)
# 2) the class to start with
#
# following this is any number of groups representing how to walk the class hierarchy
# each group is 3 items (:: separated)
# 1) Relationship type
# 1.1) op = Operation. This should be a class operation that returns a set of objects and
takes no parameters.
# 1.2) rel = relationship. This is a normal multiple relationship property of the object
(e.g. ComposedOf or InstrumentedBy)
# 1.3) rel1 = single relationship property. It returns only 1 item rather than an array (e.g.
SystemName or SystemPackagedIn)
# 2)Relationship property name (should match the type)
# 3)Base class to expect from the relationship.
#
# subscription is the list of properties to gather as metrics.
#topo
# One pair (:: separated)
# First element is the smarts class to create the container from
# Second element is the property to get the children of this container.
ICPM.classes.1=top::UnitaryComputerSystem op::getProcessors::Processor
EMC Smarts Integration Guide
24 VMware, Inc.