APM new platform requirements

[epixa]

In order to power APM entirely from the new platform, we need to complete the following:

• New platform on the server New platform foundation on server #12660
• New platform in the UI New platform foundation in the UI #16253
• Plugin services Core plugins support (server side) #18840
• License plugin License plugin #18356
• Security plugin Security plugin in the new platform #18024
• Elasticsearch service [server] Elasticsearch service #18841
• Saved object service Migrate saved object service #33587
• Application service [browser] Application service #18843
• Timepicker plugin Timepicker plugin #18845
• UI settings service UI settings service #18921

[sorenlouv]

I don't see anything obvious missing. What about the core plugins like ui/chrome - will they be available or rewritten for the new platform?

[epixa]

@sqren ui/chrome isn't a plugin, but yeah, we'll need to pass in that sort of functionality through the core contract instead of importing it like you do today. If you could list the very specific pieces of functionality that you need from chrome, that would be helpful!

[sorenlouv]

Core functionality used by APM:

ui/chrome:
getInjected
addBasePath
getUiSettingsClient

ui/metadata:
metadata

@kbn/ui-framework/components
(we should move away from this anyway)

[epixa]

That's great, thanks. Most of those things should be easy to replace.

@spalger The UI settings client is probably one bigger thing we need to sort out for the new platform. I didn't realize folks could grab that through chrome right now.

[sorenlouv]

We use the ui settings for getting the user's date format:

chrome.getUiSettingsClient().get('dateFormat:tz');

[epixa]

cc @roncohen @alvarolobato