[logstash] fix mappings

[klacabane]

Summary

Regression in mappings were introduced in previous change

• cluster_uuid was removed
• nested properties were updated to use an unsupported syntax - see relevant issue [epm] child properties of nested objects are not defined in mappings kibana#138596

Testing

• build logstash package elastic-package build
• start a stack elastic-package stack up -v -d --version 8.5.0-SNAPSHOT
• start logstash service elastic-package service up -v
• install elasticsearch and logstash packages
• logstash appears in standalone and elasticsearch cluster

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-11-16T11:15:43.507+0000

• Duration: 17 min 30 sec

Test stats 🧪

Test	Results
Failed	0
Passed	25
Skipped	0
Total	25

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (2/2)	💚
Files	100.0% (6/6)	💚 2.53
Classes	100.0% (6/6)	💚 2.53
Methods	100.0% (46/46)	💚 9.101
Lines	87.558% (190/217)	👎 -4.139
Conditionals	100.0% (0/0)	💚

[miltonhultgren]

When I first clicked the pipelines page I got this error:

[2022-11-15T14:26:52.411+00:00][ERROR][plugins.monitoring.monitoring] TypeError: Cannot read properties of undefined (reading 'firstSeen')
    at getPipeline (/usr/share/kibana/x-pack/plugins/monitoring/server/lib/logstash/get_pipeline.js:100:109)
    at Object.handler (/usr/share/kibana/x-pack/plugins/monitoring/server/routes/api/v1/logstash/pipeline.js:80:85)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at handler (/usr/share/kibana/x-pack/plugins/monitoring/server/plugin.js:358:28)
    at Router.handle (/usr/share/kibana/node_modules/@kbn/core-http-router-server-internal/target_node/src/router.js:163:30)
    at handler (/usr/share/kibana/node_modules/@kbn/core-http-router-server-internal/target_node/src/router.js:124:50)
    at exports.Manager.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
    at Object.internals.handler (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:46:20)
    at exports.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:31:20)
    at Request._lifecycle (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:371:32)
    at Request._execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:281:9)

But it quickly resolved itself. Everything else seems to work well.

[klacabane]

Was that the only error logged ? This could happen if documents are not ingested yet but I thought we added a guard for that with a user friendly message. Can you reproduce it ?

[miltonhultgren]

I tried to reproduce it but couldn't 🤷🏼 Probably fine then