Skip to content

Conversation

5hanker
Copy link

@5hanker 5hanker commented Oct 15, 2025

On the [Metrics ESS Billing] Billing dashboard, there is a mismatch in the numbers when you compare Total cost for period (ECUs) with "Cost per deployments/projects over time" or "Cost per features over time" or "ECH Capacity Costs per instance flavors over time" or "Serverless features per service types over time". This happens when you choose custom time range like "from:'2024-07-01T00:00:00.000Z',to:'2025-09-30T23:59:59.999Z". I see that its because this viz have "Drop partial intervals". We need to make the numbers consistent.

image

@5hanker 5hanker added the bug Something isn't working, use only for issues label Oct 15, 2025
@5hanker 5hanker requested a review from a team as a code owner October 15, 2025 15:47
@5hanker 5hanker added the Integration:ess_billing Elasticsearch Service Billing (Community supported) label Oct 15, 2025
@mergify mergify bot mentioned this pull request Oct 15, 2025
5 tasks
@andrewkroh andrewkroh added the documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. label Oct 15, 2025
@elasticmachine
Copy link

💚 Build Succeeded

@3kt
Copy link
Contributor

3kt commented Oct 15, 2025

@5hanker can you start the PR from upstream:main rather than from one of my former (stale) fork? I believe the diff is inaccurate because of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working, use only for issues documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. Integration:ess_billing Elasticsearch Service Billing (Community supported)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants