Explain Elastic Cloud cost changes by deployment
Separate capacity, storage and transfer changes across Elastic deployments, then review them beside the rest of your infrastructure spend. Give the team evidence for the next cost investigation.
- 14-day trial
- No credit card required
- Plans from $79/month
Spend vs Budget
Forecast $45,000 this month
The problem: why is Elastic Cloud spend hard to control?
- Observability costs can grow as deployments, storage and traffic change. Platform teams need to identify the deployment behind the bill and explain the increase without rebuilding a cross-vendor report.
The solution: a shared Elastic Cloud cost workflow
Find the deployment to investigate
Review the deployment and cost-category detail returned by Elastic Cloud to narrow the source of a reported increase.
Include observability in the same budget review
Bring Elastic Cloud into reports with connected infrastructure and AI sources so its cost stays visible to the budget owner.
Turn the report into a focused follow-up
Take the affected deployment and period back to Elastic Cloud for investigation, with finance and engineering starting from the same reported figures.
Product examples are illustrative. Usage estimates and provider-reported costs are separate measures; availability varies by connected source.
Explore the data viewBefore you connect
Check Elastic Cloud coverage and access
- Source and coverage
- Elastic Cloud ECU consumption by deployment and cost dimension, converted using a configured ECU list price and optional uniform discount.
- Required access
- Organization API key with the documented billing role. The connector reads costs; the key role must be reviewed separately.
- History and freshness
- Available historical consumption is refreshed on the scheduled sync. Dollar values depend on the configured ECU conversion; compare a closed period and your contract discount.
Limits to check
- Converted ECU amounts are not directly reported invoice dollars.
- No individual search-query cost attribution.
Who should use StackSpend for Elastic Cloud?
- Search and observability platform owners
Evaluation checklist
Check the plans and feature availability against the workflow your team needs.
- 01
Confirm the connection requirements
Review the source access, available period and data exclusions before authorizing a connection.
- 02
What to verify in your trial
Compare one deployment and cost dimension with Elastic, then validate the ECU price and any configured discount.
- 03
Agree the next review
Choose the report or alert your team will use and the person responsible for investigating a change.
StackSpend alongside Elastic Cloud billing and usage views.
Native tools provide provider-specific reporting and controls. StackSpend adds a shared monitoring workflow across connected sources.
Elastic Cloud billing and usage views
- Elastic Cloud billing and usage views focuses on its own provider data and native controls.
- Comparing other vendors requires their separate data sources and matching reporting periods.
StackSpend
- One reporting workflow for this source and your other connected providers.
- Shared reports, budgets and investigations across connected providers, subject to source coverage and plan eligibility.
Check the details before connecting.
Review connection permissions
Read the provider setup guides before sharing credentials.
Provider setup guidesSee the security details
How credentials, tenant isolation and data handling work.
Security and data handlingTalk to the team
Ask about your stack or requirements before connecting.
Contact StackSpendAbout Andrew DayElastic Cloud Cost Monitoring, answered
What is StackSpend for Elastic Cloud Cost Monitoring?
Separate capacity, storage and transfer changes across Elastic deployments, then review them beside the rest of your infrastructure spend. Give the team evidence for the next cost investigation.
Can I see which Elastic deployment changed?
The connector supplies deployment and cost-dimension consumption from the Billing Costs API. It converts ECU using a configured list price and optional uniform discount; verify these assumptions before comparing dollars with your invoice.
Is a Billing admin key the same as a read-only key?
No. The connector's read behavior and the permissions carried by the key are separate. Review the documented role and your security requirements before sharing a credential.
Can this explain an individual expensive search query?
A billing breakdown does not establish query-level root cause. Use the deployment and cost category that changed to guide a deeper investigation in your own observability tools.
For the current provider catalogue, see supported integrations.
Bring a clearer Elastic Cloud picture to your next cost review
Connect Elastic Cloud today and follow spend, budgets and alerts in one place. Review provider permissions before connecting.