This builds upon the initial Phase 1 implementation.

As an Elastic user
I want to be able to add an real browser Synthetic monitor to an Elastic Agent via an integration
So that I can centrally deploy the monitor without having to install and configure a separate Synthetic or Heartbeat Agent binary and YML file

ACs:

• User can add a Synthetic (real browser) Integration (in the same way they can other integrations)
• User can add a monitor, with the configuration of:
  • Name, frequency and other base fields
  • Monitor Script - which can be defined in one of two ways:
    • Inline (the actual script, as is currently put into the heartbeat.yml file)
    • Suite ZIP location (as implemented in Remote Zip URL support for heartbeat synthetics #271)
      • Which requires manadatory location, optional folder, optional username/password
• User can define which Elastic Agent, the integration will run on (via the integration policy -> agent policy -> agent assignment)
• The real browser Synthetic monitor will run at the given frequency, and results will appear in Uptime
• The Synthetic monitor will operate via the Docker implementation (note that this adds an environment variable to ensure Heartbeat will only run Synthetics from Docker)

Consider the AC referenced below