[Serverless Search] Update Getting Ingest Data section

[saarikabhasi]

Summary

PR updates Getting Started Ingest data row to match design .

Screen shot

Screen Recording

Getting.started.ingest.Data.row.mov

Checklist

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support

[saarikabhasi]

@elasticmachine merge upstream

[TattdCodeMonkey]

@saarikabhasi did you test that these changes don't effect dedicated? I don't think the IntegrationsPanel is used in the enterprise search getting started page that shares the search-api-panels. But it would be good to validate that nothing breaks.

[saarikabhasi]

@TattdCodeMonkey I did a quick search for IntegrationsPanel in elastic/kibana, this component is used only in search-api-panels

https://github.com/search?q=repo%3Aelastic%2Fkibana%20IntegrationsPanel&type=code

[saarikabhasi]

@elasticmachine merge upstream

[sphilipse]

Overall this looks good, but we need to address some structural issues with Serverless vs Dedicated.

[TattdCodeMonkey]

@saarikabhasi I did the same search, I was asking if you ran these code changes for dedicated as well as serverless?

It's extra work but I think it is prudent when making changes to search-api-panels to run Kibana in both modes to verify nothing breaks.

[saarikabhasi]

@TattdCodeMonkey Did a basic manual test by spinning up Kibana in dedicated. Everything looks good.

Tests I did:

• Checked the getting started page, all the links works
• Able to create a new index - API, crawler, Connector, Create API key, change language clients and tried to ingest content from the example using try in console
• Created Search applications, behavioural analytics collection, app search engine, visited few pages in stack management.

Went little extra step: Commented out SelectClient component that's being in both Serverless and dedicated. I see page break in getting started page in dedicated. Which I hope expected to happen when something breaks and I don't see same happening in dedicated with this change.

Tested same in serverless_search project. Everything looks good.

Please let me know if i missed any aspects.

[saarikabhasi]

@elasticmachine merge upstream

[TattdCodeMonkey]

LGTM with changes.

[TattdCodeMonkey]

The current FTR failures look like flakes from what I can tell. They're not test failures but it looks like the process is exiting with non-zero after the tests complete?

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: ffd811a

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
serverlessSearch	300	301	+1

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
@kbn/search-api-panels	69	66	-3

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
securitySolution	12.8MB	12.8MB	+6.4KB
securitySolutionServerless	330.6KB	336.9KB	+6.3KB
serverlessSearch	368.4KB	367.0KB	-1.4KB
total			+11.2KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
securitySolutionServerless	41.7KB	41.7KB	-1.0B

Unknown metric groups

API count

id	before	after	diff
@kbn/search-api-panels	69	66	-3

History

• 💔 Build #177732 failed 1b2d6f1
• 💔 Build #177100 failed 51da5af
• 💛 Build #176548 was flaky 71dc216
• 💛 Build #175918 was flaky 52b9b91
• 💛 Build #175130 was flaky e177582

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream