Skip to content

Conversation

@sholzhauer-es
Copy link
Contributor

Proposed commit message

Moving from weighted cost attributed to only the data tiers to a sku and utilization based attribution of cost.

  • Split dashboard into overview, data tier and features
  • Deployment statistics per cost_type
  • changed cluster_tier_contribution and cluster_tier_and_ds_contribution transforms to align tier with billing info. (hot/content --> datahot/datacontent, cold --> datacold, etc)

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

image

JohannesMahne and others added 30 commits June 26, 2025 09:22
…m_color_blind palate. Add ECU rate to the dashboard.
…Also added explanation about the rest of the config.
JohannesMahne and others added 27 commits August 8, 2025 13:55
…f both, to make it easier to identify the deployment in the dashboard.
…okup index automatically when installing the package.
* dashboard control

* updating version + DV
* adding sku and cost_type to billing data for node granularity

* working on sku with pipeline to do parsing

* downplaying version

* transform
…16185)

* Add deployment_group extraction from ESS Billing tags

- Extract chargeback_group tag value to deployment_group field in billing pipeline
- Add deployment_group to billing_cluster_cost transform group_by
- Add deployment_group field definition
- Fix transforms to use elasticsearch.cluster.name without .keyword
- Update changelog for v0.2.4

* Add deployment_group extraction using runtime mappings from ESS Billing tags

* Update dashboard with deployment_group filter and definitions

* Bump version to 0.2.5 for deployment_group feature after merging SKU/cost_type changes

* known  [bug](elastic/elasticsearch-chargeback#60) from 0.2.4
@sholzhauer-es sholzhauer-es added enhancement New feature or request breaking change labels Dec 3, 2025
@elasticmachine
Copy link

💚 Build Succeeded

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

Labels

breaking change enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants