[vishaangelova]

Relates to #8153. Part of a set of PRs for this issue, split by docs set:

• #9055: the integration policy and agent policy pages, and a new page, Open an integration's details, that other pages link to
• #9056: Security pages
• #9251: Fleet and ingest pages
• This PR: Observability pages

The PRs don't depend on each other and can merge in any order. Close #8153 after all four merge.

Summary

Two UI changes affect the steps for adding an integration:

• Starting in 9.6 (and in Serverless), selecting an integration tile opens the Add page directly instead of the integration's details page (kibana#299010). This includes the tiles in Observability and Security onboarding, which use the same Fleet card logic.
• The Ready to add your first integration? page was removed in 9.3.6, 9.4.3, and 9.5.0 (kibana#271801). In earlier releases, it only appears on Elastic Cloud when no agents are enrolled yet, and never for a few integrations with their own setup flow, such as Elastic APM.

How the steps change

• "Click Add " becomes "If the integration's Overview page opens, click Add ." The next step is the same in every version, so there's no badge.
• The separate step that asked readers to read the integration's overview is removed on the AWS service pages (EC2, S3, SQS, Kinesis), along with "Make sure you configure all required settings". The steps now match the other pages.
• "If the Ready to add your first integration? page opens, click Add integration only (skip agent installation)." This step has no applies_to badge on purpose. Even in the releases that still have it, the page only appears under the conditions above, so the step must stay conditional either way. Readers who don't see the page skip the step, and everyone reaches the same configuration page next. A badge would only add noise. Where this step was a tip or note, it's now a numbered step, because readers who see that page can't continue without it.
• The Jaeger and plaintext logs pages go through the Installed integrations tab, because selecting a tile on Browse integrations now opens the Add page instead of the installed integration's pages.

Changes

16 pages across Cloud, infrastructure and hosts, APM, and logs.

• "Ready to add" step: added where it was missing, including the standalone agent pages, because standalone agents don't enroll in Fleet, so readers on Elastic Cloud releases that still have that page can see it. Tips that described the page vaguely or told every reader to skip agent installation are replaced with the conditional step.
• Plaintext logs: the steps had readers click Install Elastic Agent, which exists only on the Ready to add your first integration? page. Readers now save the integration and add Elastic Agent from the post-save dialog.
• GCP Dataflow templates: the button is Save and continue in every version, and a new step has readers click Add Elastic Agent later, because the Dataflow template sends data directly to Elasticsearch.
• Opening Integrations and finding the tile use the same wording on all pages, following the UI writing guide. Tile names match the integration manifests.

Not changed: the Elastic GovCloud and Firehose pages, because those integrations still open their details page.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

Tool(s) and model(s) used: Cursor with Claude Opus 5.5

[github-actions]

Elastic Docs AI PR menu

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

• Review docs changes (docs-review). Status: completed, no findings. View progress.

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

[github-actions]

🔍 Preview links for changed docs

• solutions/observability/apm/apm-server/fleet-managed.md
• solutions/observability/apm/ingest/jaeger.md
• solutions/observability/cloud/gcp-dataflow-templates.md
• solutions/observability/cloud/monitor-amazon-cloud-compute-ec2.md
• solutions/observability/cloud/monitor-amazon-kinesis-data-streams.md
• solutions/observability/cloud/monitor-amazon-simple-queue-service-sqs.md
• solutions/observability/cloud/monitor-amazon-simple-storage-service-s3.md
• solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-agent.md
• solutions/observability/cloud/monitor-microsoft-azure-openai.md
• solutions/observability/cloud/monitor-microsoft-azure-with-elastic-agent.md

More links …

• solutions/observability/infra-and-hosts/collect-nginx-data-otel-integration-fleet-managed.md
• solutions/observability/infra-and-hosts/collect-nginx-data-otel-integration-standalone.md
• solutions/observability/infra-and-hosts/get-started-with-system-metrics.md
• solutions/observability/infra-and-hosts/tutorial-observe-kubernetes-deployments.md
• solutions/observability/infra-and-hosts/tutorial-observe-nginx-instances.md
• solutions/observability/logs/plaintext-application-logs.md

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

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.

[github-actions]

Docs review summary

Issue satisfaction

Satisfied. The 16 Observability pages cover the direct Add page navigation, the conditional Ready to add your first integration? step, and the wording alignment that the PR description lists.

Review coverage

• Content type: how-to and tutorial pages (step-by-step integration setup). The edits fit the existing structure.
• Checked: user focus, technical accuracy, applicability, maintainability, language, and style.
• Not checked: UI labels: not verified. This covers Installed integrations, Integration policies, Add {{agent}} to your hosts, Add {{agent}} later, Save and continue, and the Ready to add your first integration? page. Product source was not cloned in this run, and the PR description links the kibana PRs that cover them. Behavior in 9.6 and later was not checked against the kibana code.

Generated from Docs review agent · ◷

Was this review helpful? When the PR closes, add the label ai-review:helpful or ai-review:unhelpful to it.

[alexandra5000]

Nice! I left a couple of comments