Document Hosted Workflow and Agent Builder execution billing - #8145
Conversation
AI-Assisted: Drafted and verified with OpenAI Codex.
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. |
✅ 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. |
| 6. [Workflow executions](#workflow-executions) | ||
| 7. [{{agent-builder}} executions](#agent-builder-executions) |
There was a problem hiding this comment.
nit: why {{agent-builder}} just wonder
There was a problem hiding this comment.
{{agent-builder}} is a variable that renders as "Elastic Agent Builder" in the HTML output of the docs. We use variables for Elastic product names and terms to enforce consistency across the docs.
leemthompo
left a comment
There was a problem hiding this comment.
agent builder content lgtm
|
@tinnytintin10 @talboren Can you take a look at the specifics for your areas on the hosted billing page updates? From my perspective the changes look okay but would like your confirmation on how it's metered. |
|
@talboren Sorry, I see you already reviewed. Ignore! |
shainaraskas
left a comment
There was a problem hiding this comment.
approving, but please wait on review from @briannebartlett. I am particularly worried about conflating computing resources and billing dimensions (but I might be worried for nothing).
We should make sure we address the ECH pre-9.5 audience as well - see my comments below
| : An ECU is a unit of aggregate consumption across multiple resources over time. | ||
|
|
||
| Each type of computing resource (capacity, data transfer, and snapshot) that you consume has its own unit of measure. For example, capacity is measured in GB-hour, data transfer in GB, snapshot storage in GB-month and snapshot API requests in thousands of requests. | ||
| Each billing dimension has its own unit of measure. For example, capacity is measured in GB-hours, data transfer in GB, snapshot storage in GB-months, snapshot API requests in thousands of requests, and {{agent-builder}} and Workflows in executions. |
There was a problem hiding this comment.
we don't have 100% coverage on billing dimensions in this list (synthetics and inference missing at least)
other definitions use "computing resources", e.g. line 56 on this page.
Wonder if we need to split resource-based consumption and add-on usage charges or something
There was a problem hiding this comment.
@tinnytintin10 this might need to be addressed before we can merge the PR.
There was a problem hiding this comment.
Each product has its own unit of measure referred to as billing dimension. For example, computing resources, such as capacity is measured in GB-hours, data transfer in GB, and snapshot storage in GB-month, and snapshot API requests in thousands of requests.
Additionally, add-on features are measured in alternative billing dimensions such as Workflows and Agent Builder in executions, Managed Integrations in Integration hours, and Elastic Inference Service in tokens.
|
|
||
| {{agent-builder}} and [Workflows](/explore-analyze/workflows.md) on {{ech}} are currently under promotional pricing and available at no additional charge. | ||
| ```{applies_to} | ||
| stack: ga 9.5+ |
There was a problem hiding this comment.
@tinnytintin10 do you know the pricing model for Agent Builder executions on ECH prior to 9.5? I don't know much about the Agent Builder side, so I'm not sure what the model looked like and who would have this information.
There was a problem hiding this comment.
It was on promotional period, not metering in place
| ## Execution-based billing [workflows-execution-billing] | ||
|
|
||
| ```{applies_to} | ||
| stack: ga 9.5+ |
There was a problem hiding this comment.
same "what happens before 9.5" question
There was a problem hiding this comment.
@tinnytintin10 it'd be useful to clarify the pricing model (or the absence of one) for workflows in 9.3-9.4.
…nt-billing-dimensions.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
…ws.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
| @@ -58,9 +58,9 @@ Resource-based pricing | |||
| Elastic Consumption Unit (ECU) | |||
| : An ECU is a unit of aggregate consumption across multiple resources over time. | |||
There was a problem hiding this comment.
An ECU is a unit of aggregate consumption across multiple resources over time.
Summary
Closes #8144
Verification
git diff --check.Generative AI disclosure
Tool used: OpenAI Codex
Codex assisted with drafting, repository navigation, and verification against the approved billing implementation. The final changes were reviewed against the production pricing configuration and metering behavior.