Splunk® Common Information Model Add-on

Common Information Model Add-on Manual

Download manual as PDF

This documentation does not apply to the most recent version of CIM. Click here for the latest version.
Download topic as PDF

How to use these reference tables

Each topic in this section contains a use case for the data model, a breakdown of the required tags for the event objects or searches in that model, and a listing of all extracted and calculated fields included in the model.

How to read the tags tables

The tags tables communicate which tags you must apply to your events in order to make them CIM-compliant. These tags act as constraints to identify your events as relevant to this data model, so that this data is included in Pivot reports and dashboards based on this model.

There might be additional constraints outside the scope of these tables. Refer to the data model itself using its editor view in Splunk Web for required fields, field=value combinations, or base searches that the model depends on.

Ensure your data is populated in the correct dashboards and Pivot reports.

  1. Identify the CIM object relevant to your events.
  2. Observe which tags are required for that object.
  3. Observe which tags are required for any parent objects.
  4. Apply those tags to your events using event types.
  5. Repeat for any additional relevant CIM objects.

For a detailed walkthrough of these steps, see Use the CIM to normalize data at search time.

How to read the fields tables

The fields tables list the extracted and calculated fields for the event and search objects in the model and provide descriptions and expected values (if relevant) for these fields. The table presents the fields in alphabetical order, starting with the fields for the parent object in the model, then proceeding to any unique fields for child objects. The table does not repeat any fields that a child object inherits from a parent object, so refer to the parent object to see the description and expected values for that field.

Because the fields tables exclude inherited fields, many child objects have no fields listed in the table at all. Those child objects include only inherited fields from one or more of their parent objects, so there are no unique extracted or calculated fields to display. All data models inherit the fields _time, host, source, and sourcetype, so those fields are always available to you for use in developing Pivot reports and dashboards.

Use the tables to apply the Common Information Model to your data

The tables in this section of documentation are intended to be supplemental reference for the data models themselves. Use the documentation and the data model editor in Splunk Web together.

Prerequisite

You need Write access to a data model in order to browse it in its editor view. If you do not have this access, request it from your Splunk administrator.

Steps

  1. In Splunk Web, go to Settings > Data Models to open the Data Model Manager.
  2. Click a data model to view it in the Data Model Editor. There, you can see the full object hierarchy, a complete listing of constraints for each object, and full listing of all inherited, extracted, and calculated fields for each object.
  3. Compare this information with the reference tables in the documentation for descriptions and expected values of the fields in each object.

Data model editor1.png

Information available in
documentation
Information available in
Data Model Editor in Splunk Web
Required tags YES YES
Other constraints NO YES
Full object hierarchy NO YES
Inherited fields NO YES
Extracted fields YES YES
Calculated fields YES YES
Data types YES YES
Descriptions YES NO
Expected values YES NO
PREVIOUS
Support and resource links for the Splunk Common Information Model Add-on
  NEXT
Alerts

This documentation applies to the following versions of Splunk® Common Information Model Add-on: 4.3.0, 4.3.1, 4.4.0, 4.5.0


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters