Skip to content

Commit 2be2147

Browse files
gbamparopeyalkoren
andauthored
Fix typos in the normalize processor docs (#136824)
* Fix typos in the normalize processor * Add `severity_text` field to the normalized example --------- Co-authored-by: eyalkoren <[email protected]>
1 parent 9d63517 commit 2be2147

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

docs/reference/enrich-processor/normalize-for-stream.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,12 +44,12 @@ If the document is not OpenTelemetry-compliant, the processor normalizes it as f
4444
| `log.level` | `severity_text` |
4545

4646
The processor first looks for the nested form of the ECS field and if such does not exist, it looks for a top-level field with the dotted field name.
47-
* Other specific ECS fields that describe resources and have corresponding counterparts in the OpenTelemetry Semantic Conventions are moved to the `resource.attribtues` map. Fields that are considered resource attributes are such that conform to the following conditions:
47+
* Other specific ECS fields that describe resources and have corresponding counterparts in the OpenTelemetry Semantic Conventions are moved to the `resource.attributes` map. Fields that are considered resource attributes are such that conform to the following conditions:
4848
* They are ECS fields that have corresponding counterparts (either with
4949
the same name or with a different name) in OpenTelemetry Semantic Conventions.
5050
* The corresponding OpenTelemetry attribute is defined in
5151
[Semantic Conventions](https://github.com/open-telemetry/semantic-conventions/tree/main/model)
52-
within a group that is defined as `type: enitity`.
52+
within a group that is defined as `type: entity`.
5353
* All other fields, except for `@timestamp`, are moved to the `attributes` map.
5454
* All non-array entries of the `attributes` and `resource.attributes` maps are flattened. Flattening means that nested objects are merged into their parent object, and the keys are concatenated with a dot. See examples below.
5555

@@ -149,6 +149,7 @@ will be normalized into the following form:
149149
}
150150
]
151151
},
152+
"severity_text": "INFO",
152153
"body": {
153154
"text": "Hello, world!"
154155
},

0 commit comments

Comments
 (0)