Log Fields Node Layout
The log.fields node of a profile contains one subnode per log field. The layout of each field node is:
label
type
index
subindex
hierarchy_dividers
left_to_right
leading_divider
case_sensitive
derived_from_1
derived_from_2
| label |
|---|
| Type: | string |
| Values: | Unique log field label. |
| Default value: | - |
| Relevant: | always |
| Notes: | |
| type |
|---|
| Type: | string |
| Values: | agent
date
date_time
flat
hierarchical
host
page
response
size
time
URL |
| Default value: | flat |
| Relevant: | always |
| Notes: | |
| index |
|---|
| Type: | int |
| Values: | - |
| Default value: | 0 |
| Relevant: | always |
| Notes: | Technically, index/subindex are relevant only when doing index/subindex style parsing, but it's difficult to determine automatically if that is occuring, hence they are always relevant. |
| subindex |
|---|
| Type: | int |
| Values: | - |
| Default value: | 0 |
| Relevant: | always |
| Notes: | Technically, index/subindex are relevant only when doing index/subindex style parsing, but it's difficult to determine automatically if that is occuring, hence they are always relevant. |
| hierarchy_dividers |
|---|
| Type: | string |
| Values: | A string with length <=2. |
| Default value: | / |
| Relevant: | Only relevant for fields with type="hierarchical". |
| Notes: | The hierarchy_dividers node may exist in existing profiles or at profile creation time, even if the type is not "hierarchical", in this case we can ignore or delete the node! |
| left_to_right |
|---|
| Type: | boo| |
| Values: | boo| |
| Default value: | true |
| Relevant: | Only relevant for fields with type="hierarchical". |
| Notes: | The left_to_right node may exist in existing profiles or at profile creation time, even if the type is not "hierarchical", in this case we can ignore or delete the node! |
| leading_divider |
|---|
| Type: | boo| |
| Values: | - |
| Default value: | true |
| Relevant: | Only relevant for fields with type="hierarchical". |
| Notes: | The leading_divider node may exist in existing profiles or at profile creation time, even if the type is not "hierarchical", in this case we can ignore or delete the node! |
| case_sensitive |
|---|
| Type: | boo| |
| Values: | - |
| Default value: | false |
| Relevant: | always |
| Notes: | |
| derived_from_1 |
|---|
| Type: | string |
| Values: | - |
| Default value: | - |
| Relevant: | Only if the node exists and is not empty. |
| Notes: | Derived fields are automatically created by the C++. A log field which contains a derived_from_1 node should not be editable but only displayed in the GUI. |
| derived_from_2 |
|---|
| Type: | string |
| Values: | - |
| Default value: | - |
| Relevant: | Only if the node exists and is not empty. |
| Notes: | Derived fields are automatically created by the C++. A log field which contains a derived_from_2 node should not be editable but only displayed in the GUI. |