Carlos Crespo

I've been looking into this and the suggestion below works: > set json.keys_under_root: true in the module config and remove the script processor The log is ingested correctly, which makes...

@matschaffer this `input` configuration, to add extra fields at module level, isn't something we are supporting on the integration packages.

The reason why module config sets `json.keys_under_root: false` only to then copy the `json.*` in the ecs pipeline is because we need to support [non-ecs formatted logs](https://github.com/elastic/beats/blob/main/filebeat/module/kibana/log/ingest/pipeline-7.yml). The `json.*` fields...

This [bifurcation we have in the main pipeline file](https://github.com/elastic/beats/blob/main/filebeat/module/kibana/log/ingest/pipeline.yml) is only valid for [kibana

Just to be on the same page here, based on the [documentation](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-general-options.html#libbeat-configuration-fields) `input.fields` can be used to *add* new fields to the output.

Yeah. Fair point. I don't think we have either. I'm wondering if we could make Kibana, Logstash and ES packages production ready and start with them - perhaps they can...

We have identified some issues on the Infra UI related to the missing `host.hostname` field. When we link to APM services and use a filter based on `host.hostname,` it doesn't...

@ablnk Is it possible to access the environment where the error is happening? I'd like to have a closer look to the logs.

I'm getting the 502 in QA deployment with ~1800 services and ~170 dependencies, within 15m range, which I believe is still within the 7d boost window.  The map is...

The solution for this might be related to https://github.com/elastic/observability-serverless/issues/18 and [#181790](https://github.com/elastic/kibana/issues/181790)