[Synthetics] Disable browser sub-inputs by default

[miguelmartin-elastic]

Label: Enhancement

Proposed commit message

Disable browser inputs by default in the Synthetics integration package.

The synthetics/browser, synthetics/browser.network, and synthetics/browser.screenshot input streams were enabled by default, which could lead to unnecessary data collection when users create a new Synthetics integration policy without explicitly configuring these inputs.

This change sets enabled: false in the manifest files of the three browser-related data streams (browser, browser_network, browser_screenshot), bumps the package version to 1.6.0, and updates the Kibana version constraint to ^9.4.0 to ensure this behavior only applies to compatible Kibana versions.

Extra: update @elastic/obs-ux-management-team references to @elastic/actionable-obs-team in CODEOWNERS file

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 according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• Verified that creating a new Synthetics integration policy without enabling browser inputs keeps them disabled
• Verified that browser inputs can still be explicitly enabled by the user

How to test this PR locally

1. Start a local Kibana/Elasticsearch stack on version >=9.4.0.
2. Install or update the Synthetics integration package to this version (1.6.0).
3. Create a new Synthetics integration policy without enabling browser inputs.
4. Confirm that the synthetics/browser, synthetics/browser.network, and synthetics/browser.screenshot inputs are disabled by default.

Steps in detail:

1. Start the stack and install the package:

elastic-package stack up -d
cd packages/synthetics
elastic-package install

2. Verify browser inputs are disabled by default:

curl -sk -u elastic:changeme 'https://localhost:5601/api/fleet/epm/packages/synthetics/1.6.0' \
  | python3 -c "
import sys, json
pkg = json.load(sys.stdin)['item']
for ds in pkg.get('data_streams', []):
    for s in ds.get('streams', []):
        if 'browser' in ds.get('dataset', ''):
            print(f\"{ds['dataset']:25s} enabled={s['enabled']}\")
"

Expected output:

browser                   enabled=False
browser.network           enabled=False
browser.screenshot        enabled=False

3. Tear down:

elastic-package stack down

Related issues

• Closes [Synthetics] Disable browser inputs by default in package spec #15696
• [Synthetics] Explicitly enable sub-inputs for browser monitors in integration policies kibana#239747

Screenshots

N/A

[miguelmartin-elastic]

More info here: #15696 (comment)

[miguelmartin-elastic]

Additional testing:

I created a monitor using the upgraded integration package (1.6.0) and the latest Kibana main, which enables the data streams explicitly, and verified that it works correctly

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 0c5d6ee

History

• 💚 Build #39188 succeeded cd459b8
• 💔 Build #39178 failed ace94e5
• 💚 Build #39136 succeeded 35037c1

[mgiota]

@miguelmartin-elastic Thanks for the clear "How to test" steps.

I verify browser sub-inputs are disabled by default in the latest Synthetics 1.6 package version.

1.5 - enabled

1.6 - disabled

[mgiota]

I created a monitor using the upgraded integration package (1.6.0) and the latest Kibana main

Curious to know how you did the end to end testing with Kibana. Here's a documentation I created a while ago. I would like to know how you do the end to end testing with both integrations and kibana repos

[miguelmartin-elastic]

Curious to know how you did the end to end testing with Kibana. Here's a documentation I created a while ago. I would like to know how you do the end to end testing with both integrations and kibana repos

Cursor figured out the existence of elastic-stack and used it to spin up the entire stack using containers.

After that, I also wanted to test with different versions of Kibana, so I asked it to find the easiest/fastest/simplest way and to create a rule for it, and this was the output:
upload-package-local-kibana.txt

[mgiota]

@miguelmartin-elastic That's awesome! Option 2 in my documentation, in just seconds!