Skip to content

Refine Prometheus Remote Write page and Managed inputs naming#632

Merged
vishaangelova merged 3 commits into
mainfrom
7155-managed-inputs-content
Jul 16, 2026
Merged

Refine Prometheus Remote Write page and Managed inputs naming#632
vishaangelova merged 3 commits into
mainfrom
7155-managed-inputs-content

Conversation

@vishaangelova

@vishaangelova vishaangelova commented Jun 30, 2026

Copy link
Copy Markdown
Member

Summary

Builds on #630 with content and metadata refinements to the new Managed inputs docs based on feedback from support.

Changes

  • Rewrite the Prometheus Remote Write page to present the Managed Prometheus Remote Write Endpoint as a distinct managed input (separate from the Managed OTLP Endpoint), and recommend it over sending metrics directly to the Elasticsearch PRW endpoint on Serverless.
  • Set the applies_to for the PRW page to serverless.observability: preview.
  • Apply consistent naming on the landing page and the PRW page.

Related to elastic/docs-content#7155

@vishaangelova
vishaangelova requested review from a team and theletterf as code owners June 30, 2026 23:15
@github-actions

github-actions Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

✅ 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

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.

@florent-leborgne florent-leborgne 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.

LGTM

Comment thread docs/reference/motlp/index.md Outdated
Comment thread docs/reference/motlp/prometheus-remote-write.md Outdated
Comment thread docs/reference/motlp/prometheus-remote-write.md Outdated
Comment thread docs/reference/motlp/prometheus-remote-write.md Outdated
Comment thread docs/reference/motlp/index.md Outdated
Comment thread docs/reference/motlp/index.md Outdated
Comment thread docs/reference/motlp/index.md Outdated
Comment thread docs/reference/motlp/index.md Outdated
Comment thread docs/reference/motlp/prometheus-remote-write.md Outdated
Comment thread docs/reference/motlp/prometheus-remote-write.md Outdated
Comment thread docs/reference/motlp/prometheus-remote-write.md Outdated
@perk

perk commented Jul 3, 2026

Copy link
Copy Markdown
Member

Hey, I don't think that's an observability serverless onlny feature - it's already available for security one as well.

@jlind23

jlind23 commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

@vishaangelova can we resurrect this please? 🙏🏼

- Rename the Prometheus Remote Write page to "Managed Prometheus Remote
  Write endpoint" and present it as a distinct managed input.
- Set the PRW page applies_to to serverless observability and security GA
  (confirmed GA on Serverless, available for Security too).
- Use "data" instead of "telemetry" and sentence-case "managed inputs".
- Broaden the Managed OTLP Endpoint description to include the EDOT Cloud
  Forwarder and any OTLP-compliant shipper.
- Explain how authentication differs from the direct Elasticsearch PRW
  endpoint.

Co-authored-by: Cursor <cursoragent@cursor.com>
@vishaangelova
vishaangelova force-pushed the 7155-managed-inputs-content branch from e2b45b4 to 4466a7e Compare July 16, 2026 07:16
Document the counter/gauge inference rules directly in the "How
Prometheus data appears in Elasticsearch" section, while keeping the
cross-link to the Elasticsearch PRW docs for the full mapping detail.

Co-authored-by: Cursor <cursoragent@cursor.com>

@lucabelluccini lucabelluccini left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

On top of the comments done inline, I think there are several commonalities with OTLP Endpoint (they share the same underlying arch). Example:

  • Rate limiting
  • Failure Store

When this will be available on ECH, we'll need to mention also the limitations regarding the IP Filtering and Private connections (as OTLP).

Comment thread docs/reference/managed-inputs/prometheus-remote-write.md
Comment thread docs/reference/managed-inputs/prometheus-remote-write.md
Comment thread docs/reference/managed-inputs/prometheus-remote-write.md Outdated
Comment thread docs/reference/managed-inputs/prometheus-remote-write.md Outdated
- Point users to the Prometheus endpoint in the Cloud console (not the
  removed "Ingest" option) and use the .ingest domain; the copied value
  already includes the /api/v1/write path, so drop the append step.
- Rename the placeholder to <prometheus-endpoint> for the full URL.
- Mark the custom data stream routing step as optional.

Co-authored-by: Cursor <cursoragent@cursor.com>

@lucabelluccini lucabelluccini left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks @vishaangelova
I'm approving in light of what I know/I've been told about Managed Ingest - PRW.
For sure the PMs/Eng will know more about it.

@vishaangelova
vishaangelova merged commit 7583e4f into main Jul 16, 2026
9 checks passed
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.

Restructure EDOT docs: add a "Managed inputs" parent for Managed OTLP Endpoint and Prometheus Remote Write

7 participants