config is now rooted under "schema" key

[stuartnelson3]

Update the key under which the apm-server is serialized when sent to kibana.

curl --request POST \
  --url http://localhost:5603/api/apm/fleet/apm_server_schema \
  --header 'Authorization: Basic YWRtaW46Y2hhbmdlbWU=' \
  --header 'Content-Type: application/json' \
  --header 'kbn-xsrf: true' \
  --data '{
	"schema": {
		"apm-server.host": "0.0.0.0:8200",
		"apm-server.rum.enabled": true,
		"output.ssl.enabled": true
	}
}'

cc @ogupte

How to test these changes

Note: This pr supersedes changes originally introduced in #5481. The format listed above is, at the time of writing, the correct format for sending the config to kibana.

Running apm-server under fleet, start an agent that requests its config from apm-server. Update the config, and verify that the timeseries has been ingested into elasticsearch.

[apmmachine]

💚 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

• Build Cause: Pull request #5544 updated

• Start Time: 2021-06-28T10:02:06.088+0000

• Duration: 38 min 13 sec

• Commit: a564003

Test stats 🧪

Test	Results
Failed	0
Passed	6140
Skipped	106
Total	6246

Trends 🧪

[axw]

/test

[axw]

The test instructions reference #5481 and agent config. Isn't this related to #5424? Do they both need to be on the test plan, or can we close this one?

[simitt]

Yes they are covering the same, removing the test label from this one.