[Meta] Uptime server enhancements for synthetics service

[shahzad31]

[WIP] This is still a work in progress, i will add few more items in the list

This issue is to track all the requirement/enhancements we need in Kibana uptime server code to interact with synthetics service and respective UI code in the uptime app.

Feature Flag

• [Uptime] Hide Synthetics Service Setup and Installation behind a feature flag #421 Add a feature flag that will be used via config file to enable all the synthetics service functionality on server side and ui

Data model:

• Create uptime monitors saved object data model #396
  we will have to define data model to save uptime monitor configuration, we will leverage kibana saved objects apis to do that.
  Example monitor attributes are
  id, Name, type, urls etc all the data that user will define while creating a monitor will need to be saved in a saved object , detailed options can be found here
  https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-heartbeat-options.html
• Creating io-ts types for synthetics monitors. kibana#120105
• Use Authorized Saved Objects Client #420

Task manager

• Create a schedule Task to push uptime monitor configurations periodically  #397
  We will need to define a scheduled task using Kibana task manager, which will run periodically to push monitor configurations to the synthetics service
• [Uptime] Make Synthetics Service sync task interval configurable kibana#121233

API Key Generation

• Kibana API key generation for synthetic service #398
  We need to pass an API key generated by kibana to the synthetic service, that will be used by heartbeat to communicate with elasticsearch.
• [Uptime synthetics service] Skip api key on startup kibana#119990
• [Bug] Handle error when Index is used without a configured API key #419

ES Hosts determination

• Determine es hosts for synthetics service communication #399
  We will need to write a helper function to determine es hosts, so that those can be fetched and pass to the synthetics service.

Generate index templates

• Generate synthetics data index templates #405
  Using fleet api we need to install synthetics integration package to install proper data stream index templates required to query uptime data

Mtls communication with service

• Use Mtls to communicate with synthetics service #436

Add a route to get service locations

• Using manifest file config, we need to add a route to get available service locations

Service Interface

• [Uptime] Push monitor configs to Synthetics Service #422
• [Uptime] enabled key is not pushed to synthetics service when it is false #424
• [Uptime] Added a synthetics service handler in uptime kibana#119843
• Add Route to get service locations #423

Monitor CRUD Routes

We will need following routes in the server side to meet UI requirements

• Create monitor and push it to service Create monitor route for synthetic service #401
• Edit monitor and update the service Edit monitor route for synthetic service #402
• Delete monitor and ask service to delete it as well Delete Monitor route for synthetics service #403
• Add data validation to routes Add data validation to monitor CRUD routes #410

[shahzad31]

Closing this as pieces needed for tech preview are already done !!