[ess_billing] Clarify integration covers Hosted, Serverless, and cloud connected usage

[briannebartlett]

Summary

• Add a Supported Elastic Cloud products section to the ESS Billing integration docs clarifying coverage for Hosted deployments, Serverless projects, Cloud Connect usage (e.g., EIS), and other org-level services
• Update package/manifest copy to use Elastic Cloud Billing API terminology instead of legacy "Elasticsearch Service" framing
• Clarify that ess.billing.deployment_* fields represent any billed instance type (backward-compatible naming)
• Fix typo: "Cloud Hosted of Serverless" → "Cloud Hosted or Serverless"

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

• Docs-only change; verify README renders correctly on docs preview
• Confirm manifest description updates appear in Fleet integration picker

Made with Cursor

[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.

[elastic-vault-github-plugin-prod]

✅ All changelog entries have the correct PR link.

[infra-vault-gh-plugin-prod]

💔 Build Failed

• Buildkite Build
• Commit: d646bcb

Failed CI Steps

• Check integrations ess_billing

History

[github-actions]

TL;DR

Check integrations ess_billing failed because packages/ess_billing/docs/README.md is out of sync with the generated README. The PR updates the rendered README, but the source template still renders the previous content.

Remediation

• Move the README text changes into packages/ess_billing/_dev/build/docs/README.md instead of only editing packages/ess_billing/docs/README.md.
• Run elastic-package build from packages/ess_billing, then commit the regenerated packages/ess_billing/docs/README.md.

Investigation details

Root Cause

This is a generated documentation drift failure, not an integration runtime failure. Repository documentation states that package docs are written as templates under _dev/build/docs/*.md and processed by elastic-package build into docs/ (docs/extend/documentation-guidelines.md:27-29).

The PR changes packages/ess_billing/docs/README.md directly, including the new “Supported Elastic Cloud products” section and Elastic Cloud wording, but the build regenerated the README from the old template content and found that the committed rendered file no longer matches.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/45649
• Job/step: Check integrations ess_billing
• Command: .buildkite/scripts/test_one_package.sh packages/ess_billing origin/main d646bcba3280806f8c05d877aed54e64c29610d8
• Key log excerpt:

--- 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 match

Verification

Not run locally; the Buildkite log includes the full README drift diff, and the package documentation generation rule identifies _dev/build/docs/README.md as the source file to update.

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.