[ess_billing] Clarify integration covers Hosted, Serverless, and cloud connected usage#20020
Conversation
Make it explicit that org-level billing data includes Hosted deployments, Serverless projects, and cloud connected usage—not just legacy ESS deployments. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
✅ 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. |
This comment has been minimized.
This comment has been minimized.
TL;DR
Remediation
Investigation detailsRoot CauseThis is a generated documentation drift failure, not an integration runtime failure. Repository documentation states that package docs are written as templates under The PR changes Evidence
--- want
+++ got
@@ -2,18 +2,5 @@
-The Elasticsearch Service Billing integration (also known as the **Elastic Cloud billing integration**) lets you monitor usage and costs for your entire **Elastic Cloud organization**.
-## Supported Elastic Cloud products
-This integration reports **organization-level** billing data.
+The Elasticsearch Service Billing integration allows you to monitor Elasticsearch Service usage and costs.
...
Error: checking package failed: checking readme files are up-to-date failed: files do not matchVerificationNot run locally; the Buildkite log includes the full README drift diff, and the package documentation generation rule identifies What is this? | From workflow: PR Buildkite Detective Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. |
andrewkroh
added
documentation
3kt
left a comment
3kt
left a comment
There was a problem hiding this comment.
Couple NIT - good otherwise :)
Co-authored-by: Alexis Charveriat <alcharveriat@gmail.com>
|
Thank you @3kt! |
sholzhauer-es
left a comment
sholzhauer-es
left a comment
There was a problem hiding this comment.
all good from my perspective, good clearifications on doc side 👍
Fix README (_dev)
|
✅ All changelog entries have the correct PR link. |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
History
|
|
Tick the box to add this pull request to the merge queue (same as
|
|
Package ess_billing - 1.9.1 containing this change is available at https://epr.elastic.co/package/ess_billing/1.9.1/ |
5 participants
Summary
ess.billing.deployment_*fields represent any billed instance type (backward-compatible naming)Motivation
We get frequent questions about whether this integration applies to Hosted vs. Serverless. The integration has supported Serverless since v1.5.0, but the docs still read as ESS/deployment-only. This change makes org-wide coverage explicit without renaming the integration package.
Test plan
Made with Cursor