Skip to content
This is an archived version of the documentation downloaded from LogScale Documentation Archives. Up to date documentation, and documentation for later versions, is available on LogScale Documentation

### Understanding Schema Requirements

Schemas contain a collection of field mappings. Every mapping will contain tag conditions to identify the event that the mapping should be applied to. Each event can be matched with at most one mapping, hence you need to ensure that the set conditions used in all mappings are not ambiguous. See following examples of two mappings that belong to one schema:

Example Mapping 1 | Example Mapping 2 | Explanation
--- | --- | ---
#vendor = A | #vendor = A #other = X | Invalid because they share the same condition #vendor = A
#vendor = A | #other = X | Invalid because there is no common field
#vendor = A | #vendor = B | Valid because they share a common field, but with different values
#vendor = A #other1 = X | #vendor = B #other2 = Y | Valid because they share a common field (#vendor), but with different values

A good rule of thumb is to ensure that all your mappings share at least one common tag field, but with different required values on each mapping.

#### Enter search term