Remove mapping for field faas.trigger #2192
Description
Summary
I would like to remove the mapping for the field faas.trigger of type nested.
Motivation:
- The field faas.trigger can only accept a single object like you can see in the apm code at here
- Nested documents and queries are typically expensive
- the field
faas.triggeris an object in ECS but it maps to a single string in Otel like documented at issue and in the Otel docs - Avoiding unnecessary
nestedfields should make it easier to supportsubobjects: falsein the project Logs+ for default o11y mappings.
Detailed Design:
Provide additional details around the design of the proposed changes.
- Field names:
faas.trigger - Example values for the fields
"trigger": {
"request_id": "10",
"type": "http"
}
}- Suggested appropriate datatypes
suggested mapping. Notice the change
{
"mappings": {
"properties": {
"faas": {
"type": "object"
},
"mappings": {
"properties": {
"trigger": {
"type": "object"
},
"mappings": {
"properties": {
"request_id": {
"type": "keyword"
},
"type": {
"type": "keyword"
}
}
}
}
}
}
}
}- Any example events that map to the proposed use case(s)
{
"faas": {
"trigger": {
"request_id": "10",
"type": "http"
}
}
}or
{
"faas.trigger.request_id": "10",
"faas.trigger.type": "http"
}