Reference Guide

Property Description
providers for the NameSpace of this instance. For DMTF-dened instances, the preferred
algorithm must be used with the <OrgID> set to CIM.
MetricDenitionId
The key of the BaseMetricDenition instance for this CIM_BaseMetricValue instance value.
MetricValue
The value of the metric represented as a string. Its original data type is specied in
CIM_BaseMetricDenition.
TimeStamp
Identies the time when the value of a metric instance is computed. Note that this is
dierent from the time when the instance is created. For a given CIM_BaseMetricValue
instance, the TimeStamp changes whenever a new measurement snapshot is taken if
Volatile is true. A managmenet application may establish a time series of metric data by
retrieving the instances of CIM_BaseMetricValue and sorting them according to their
TimeStamp.
Volatile
If true, Volatile indicates that the value for the next point in time may use the same object
and just change its properties (such as the value or timestamp). If false, the existing objects
remain unchanged and a new object is created for the new point in time.
DCIM_LogEntry
Property Description
CreationTimeStamp
A LogEntry may include a timestamp for the entry.
ElementName
A user-friendly name for the object. This property allows each instance to dene a user-
friendly name in addition to its key properties, identity data, and description information.
NOTE: The Name property of ManagedSystemElement is also dened as a user-
friendly name. But, it is often subclassed to be a Key. It is not reasonable that the
same property can convey both identity and a user-friendly name, without
inconsistencies. Where Name exists and is not a Key (such as for instances of
LogicalDevice), the same information can be present in both the Name and
ElementName properties.
InstanceID
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely
identies an instance of this class. To ensure uniqueness within the NameSpace, the value
of InstanceID should be constructed using the following preferred algorithm:
<OrgID> : <LocalID>
Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> must
include a copyrighted, trademarked, or otherwise unique name that is owned by the
business entity that is creating or dening the InstanceID or that is a registered ID assigned
to the business entity by a recognized global authority. (This requirement is similar to the
<Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure
uniqueness, <OrgID> must not contain a colon (:). When using this algorithm, the rst colon
to appear in InstanceID must appear between <OrgID> and <LocalID> . <LocalID> is chosen
by the business entity and should not be reused to identify dierent underlying (real-world)
elements. If the above preferred algorithm is not used, the dening entity must assure that
the resulting InstanceID is not reused across any InstanceIDs produced by this or other
providers for the NameSpace of this instance. For DMTF-dened instances, the preferred
algorithm must be used with the <OrgID>set to CIM.
RecordData
A string containing LogRecord data. If the corresponding RecordFormat property is
<empty>, or cannot be parsed according to the recommended format, RecordData should
be interpreted as a free-form string. If the RecordFormat property contains parseable
format information (as recommended in the RecordFormat Description qualier), the
RecordData string SHOULD be parsed in accordance with this format. In this case,
206 Dell Command | Monitor10.1.0 classes and properties