Configure network availability monitoring (NAM) via Settings 2.0 API (workaround)

Monaco doesn't support Synthetic API v2, but you can configure Synthetic monitors API v2 via the Settings API.

Token configuration

To use Synthetic API v2, you need a token that has at least following permissions:

  • Write settings (settings.write)
  • Read settings (settings.read)
  • Access problem and event feed, metrics, and topology (DataExport)

Monitor configuration

Definitions of network availability monitoring (NAM) are covered by the following schemas:

The easiest way to create a new NAM configuration is to create it on the environment, get its configuration by downloading settings, and filtering for the settings you need.

List the required configuration in the config.yaml file. Each configuration needs to be in a separate JSON file. The following is an example (where values under config/template need to point to your specific configuration):

configs:
- id: NAM-config
  config:
    template: monitor-config.json
  type:
    settings:
      schema: builtin:synthetic.multiprotocol.config
      scope: MULTIPROTOCOL_MONITOR-D48EB7B8D7BC7B71
- id: NAM-name
  config:
    template: monitor-name.json
  type:
    settings:
      schema: builtin:synthetic.multiprotocol.name
      scope: MULTIPROTOCOL_MONITOR-D48EB7B8D7BC7B71
- id: NAM-outage
  config:
    template: monitor-outage.json
  type:
    settings:
      schema: builtin:synthetic.multiprotocol.outage-handling
      scope: MULTIPROTOCOL_MONITOR-D48EB7B8D7BC7B71
- id: NAM-thresholds
  config:
    template: monitor-thresholds.json
  type:
    settings:
      schema: builtin:synthetic.multiprotocol.performance-thresholds
      scope: MULTIPROTOCOL_MONITOR-D48EB7B8D7BC7B71
- id: NAM-scheduling
  config:
    template: monitor-scheduling.json
  type:
    settings:
      schema: builtin:synthetic.multiprotocol.scheduling
      scope: MULTIPROTOCOL_MONITOR-D48EB7B8D7BC7B71

Related topics