Refine Prometheus Remote Write page and Managed inputs naming#632
Conversation
🔍 Preview links for changed docs |
✅ 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. |
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
bd69249 to
ef110d9
Compare
|
Hey, I don't think that's an |
|
@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>
e2b45b4 to
4466a7e
Compare
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
left a comment
There was a problem hiding this comment.
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).
- 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
left a comment
There was a problem hiding this comment.
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.
Summary
Builds on #630 with content and metadata refinements to the new Managed inputs docs based on feedback from support.
Changes
applies_tofor the PRW page toserverless.observability: preview.Related to elastic/docs-content#7155