Move HttpService functionality from Legacy to New platform

[mshustov]

Having #39047 merged we can start moving some pieces of the HTTP server functionality to the new platform.
The task requires investigation to create a list of functionality that is ready to be moved over:

• HttpMixin (hapi lifecycle events)
• LoggingMixin (logging via good)
• request meta-information system api, kibana-xsrf, etc.
• etc.

[elasticmachine]

Pinging @elastic/kibana-platform

[joshdover]

Need to investigate to figure what is needed now

[mshustov]

Turned out, the legacy server performed a lot of work besides working as HTTP service. There is a list of the created issues to strip off functionality.

Require migration:

CSP

config validation, default CSP rules
link: https://github.com/elastic/kibana/tree/master/src/legacy/server/csp
issue: #50644

i18n

collects translation files and initializes kbn/i18n.
link: https://github.com/elastic/kibana/tree/master/src/legacy/server/i18n
issue: #50647

Http

• xsrf &version, name header check Migrate Kibana specific headers checks. #50656
• default route validation & redirection Migrate default route redirection #50658
• provides API to serve static files Introduce HttpResource service #50654
• provides rendering service HTML page rendering service #41964
• trailing slash route redirection Kibana server doesn't redirect URL with trailing slashes  #45528

https://github.com/elastic/kibana/tree/master/src/legacy/server/http

Logging

link: https://github.com/elastic/kibana/tree/master/src/legacy/server/logging
data collection:

• ops metrics logging
• request/response logging
  Log HTTP requests, responses #13241

infrastructure

• filtering of log output
• log formation
• log rotation
  [8.0] Remove @kbn/legacy-logging #50660

Sample data

Sample data sets for demo purposes when a new user starts working with Kibana and doesn't have any data ingested.
link: https://github.com/elastic/kibana/tree/master/src/legacy/server/sample_data
issue: #50675
not sure about owner

Saved Objects

public interface
issue: #33587

Status

Server status, status page
link: https://github.com/elastic/kibana/tree/master/src/legacy/server/status
issue: #41983

Usage collector

collects observable runtime data
link: https://github.com/elastic/kibana/tree/master/src/legacy/server/usage
issue: #46924

Config

link: https://github.com/elastic/kibana/tree/master/src/legacy/server/config
deprecations
issue: #40255
unused config values check
#50680

Non-platform team features

I can be wrong about ownership

@elastic/kibana-operations plugins:

• SASS
  re-build sass assets on dev server
  link: https://github.com/elastic/kibana/tree/master/src/legacy/server/sass

• Warnings
  filters Deprecation warnings
  https://github.com/elastic/kibana/tree/master/src/legacy/server/warnings

• Keystore
  used only by CLI tools. can be moved to a separate package. or keep in legacy for a while https://github.com/elastic/kibana/tree/master/src/legacy/server/keystore

• PID file
  creation & lifecycle management
  https://github.com/elastic/kibana/tree/master/src/legacy/server/pid

• Config path & data path
  used by internal cli tools
  https://github.com/elastic/kibana/tree/master/src/legacy/server/path

• Utils/prompt
  utils to handle user input via CLI
  https://github.com/elastic/kibana/tree/master/src/legacy/server/utils

@elastic/kibana-app / @elastic/kibana-app-arch team plugin:

• URL shortening
  https://github.com/elastic/kibana/tree/master/src/legacy/server/url_shortening
  issue: NP migration: Url shortener service #50775

[mistic]

I'm not sure about the keystore. @tylersmalley is every item listed above correctly assigned to the operations team?

[tylersmalley]

SASS

This does not need migrated over, as we will be moving back to importing via JS in the new platform (#42185 (comment)).

Warnings

Needs confirmed, but I believe this can go away since we are now running node with --no-warnings (https://github.com/elastic/kibana/blob/master/bin/kibana#L24)

Keystore

issue: #52107

PID file

issue: #52108

Config path & data path

Is there already something for this in the new platform to read from the kibana.yml?

Utils/prompt

As far as I can tell, this is just used in the keystore and can be removed as part of #52107

[mshustov]

Config path & data path

#51478 moved them under new platform src/core/server/path/index.ts.

Is there already something for this in the new platform to read from the kibana.yml?

There is only config service coupled with legacy infrastructure.