Skip to content

[Observability] Add known issue: Synthetics browser monitors on private locations fail on 9.5.0 - #7714

Open
shahzad31 wants to merge 3 commits into
mainfrom
synthetics-pl-browser-known-issue-9.5
Open

[Observability] Add known issue: Synthetics browser monitors on private locations fail on 9.5.0#7714
shahzad31 wants to merge 3 commits into
mainfrom
synthetics-pl-browser-known-issue-9.5

Conversation

@shahzad31

Copy link
Copy Markdown
Contributor

Summary

Adds an {{observability}} known issue: Synthetics browser (journey) monitors fail to run on Fleet-managed private locations when the private location's Elastic Agent is on 9.5.0.

This is the Observability/Synthetics-facing counterpart to the Elastic Agent known issue:

The entry covers:

  • Symptom — no results in the Synthetics UI; agent reports the browser component permanently failed with missing required field accessing 'heartbeat.monitors.0.schedule'.
  • Scope — browser monitors on private locations only; lightweight (HTTP/TCP/ICMP) and Elastic-managed-location monitors are unaffected.
  • Cause — Heartbeat runs under the OTel runtime by default in 9.5.0, which rejects the schedule-less browser.network / browser.screenshot data-routing sub-streams.
  • Workaround — pin Heartbeat to the process runtime via a Fleet agent policy override, including a zero-downtime pre-upgrade note for customers on 9.4.x.

@shahzad31
shahzad31 requested a review from a team as a code owner August 3, 2026 20:33
@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

🔍 Preview links for changed docs

@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Elastic Docs Style Checker (Vale)

Summary: 1 suggestion found

💡 Suggestions (1): Optional style improvements. Apply when helpful.
File Line Rule Message
release-notes/elastic-observability/known-issues.md 34 Elastic.Semicolons Use semicolons judiciously.

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

@mdbirnstiehl mdbirnstiehl left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of small style suggestions for your consideration, otherwise LGTM.

Comment thread release-notes/elastic-observability/known-issues.md Outdated
Comment thread release-notes/elastic-observability/known-issues.md Outdated
shahzad31 and others added 2 commits August 3, 2026 23:07
Co-authored-by: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com>
Co-authored-by: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants