simitt

related: https://github.com/elastic/package-spec/issues/340

WIP branch for defining ECS fields: https://github.com/elastic/ecs/pull/532 Initial draft for visualization: Initial draft for event of type `package` (updated with information provided by @SergeyKleyman ): ```//Event structure in ES: {...

Apologies for coming back to you that late. The `bundle_filepath` is expected to be working also with a relative path.

@felixbarny can we close this issue then and avoid specific handling for this edge case?

Making it more resilient without implementing a specific handling for Spring Reactive sounds like the right thing to do; let's keep it open then.

@sheeshmohsin have you seen [APM Server on cloud-on-k8s](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-apm-server.html)? Let us know if that works for you.

@IzekChen you can follow the [APM Server on ECK custom configuration guide](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-apm-server.html#k8s-apm-customize-configuration) to set any custom APM Server configuration, e.g. ``` spec: ... config: apm-server.jaeger.grpc.enabled: true ```

You would also need to specify the port, so you would end up with a configuration similar to: ``` ... spec: ... config: apm-server.jaeger.grpc.enabled: true apm-server.jaeger.grpc.host: "0.0.0.0:14250" http: service: spec:...

ES is going to write to `.logs-deprecation-elasticsearch` - let's consider writing to `.logs-deprecation-apm` to be aligned.

Nothing to link to yet; good question around the data stream index template - this still needs to be figured out.