[Synthetics] Add synthetics/api input + api / api.network data streams

[shahzad31]

Proposed commit message

Adds the Fleet integration package side of API Journey monitors so private locations can deliver monitor.type: api policies to Heartbeat. Companion to:

• feat: multi step api runner synthetics#997 — agent-side apiJourney(...) DSL using Playwright's APIRequestContext (no browser launch).
• feat(heartbeat): add api monitor type for synthetics API journeys beats#50802 — Heartbeat monitor.type: api (alias synthetics/api) input.
• [Synthetics] Add API Journey monitor type !! kibana#270874 — UI / SO / project-monitor wiring; explicitly waits on this PR.

The Kibana PR has a TODO in format_synthetics_policy.ts: inputs.find(input.type === 'synthetics/api') resolves to undefined until a synthetics >= 1.7.0 package is installed, so private-location API monitors return hasInput: false and surface a "package needs upgrade" warning. That PR also explicitly says the new input must be designed fresh, not forked from synthetics/browser, because the var schema differs.

What's in this PR

• manifest.yml: bump 1.6.1 → 1.7.0 and add synthetics/api input.

• New data stream api (dataset api) — journey/step events for API monitors. ILM 30d hot / 365d delete (matches browser). Vars are the API-correct subset of browser:

  • drops screenshots, throttling.config, synthetics_args because (*SourceJob).extraArgs in feat(heartbeat): add api monitor type for synthetics API journeys beats#50802 strips --sandbox, --screenshots, --throttling/--no-throttling for monitor.type: api.
  • keeps playwright_options and ignore_https_errors (both supported by Playwright's APIRequestContext).
  • default type: api.
  • fields mirror browser, with monitor.type: api, a new synthetics.journey.type keyword (emitted by synthexec/synthtypes.go in feat(heartbeat): add api monitor type for synthetics API journeys beats#50802 and JSONReporter in feat: multi step api runner synthetics#997), and the Chromium-only browser.experience / browser.relative_trace groups removed.

• New data stream api_network (dataset api.network) — the dataset synthexec/enrich.go in feat(heartbeat): add api monitor type for synthetics API journeys beats#50802 routes API-journey journey/network_info events to. ILM 1d hot / 14d delete (matches browser_network). Fields mirror browser_network (TLS / server / resolve groups already covered by ECS) with the same journey.type addition. No stream-level vars — inherits from the parent synthetics/api input, same model as browser_network.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current.
• N/A — no dashboards added.

How to test this PR locally

cd packages/synthetics
elastic-package format
elastic-package check       # lint + build, both must be green

End-to-end (requires the companion PRs):

1. Build a Heartbeat with feat(heartbeat): add api monitor type for synthetics API journeys beats#50802 and a @elastic/synthetics from feat: multi step api runner synthetics#997.
2. Build a Kibana with [Synthetics] Add API Journey monitor type !! kibana#270874 and install this synthetics-1.7.0 package.
3. Create an API Journey monitor in the Synthetics UI with a private location.
4. Verify the Fleet policy lands with inputs[].type: synthetics/api enabled and Heartbeat executes the journey.
5. Verify journey/step events flow into synthetics-api-default and per-request network events flow into synthetics-api.network-default.

Related issues

• Requires feat: multi step api runner synthetics#997
• Requires feat(heartbeat): add api monitor type for synthetics API journeys beats#50802
• Requires [Synthetics] Add API Journey monitor type !! kibana#270874
• Closes the "Required follow-up: Fleet synthetics integration package" callout in [Synthetics] Add API Journey monitor type !! kibana#270874

Out of scope / follow-ups

• Test config under _dev/test/... (the package currently has none — separate effort).
• The apiFormatters map in elastic/kibana's private_formatters/formatters.ts — needs to be authored against the var names declared here, not by reusing browserFormatters.

Made with Cursor

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: bbfa853