chargeback: package-spec alignment for alerting templates

JohannesMahne · JohannesMahne · commit 5d1d3d581d11 · 2026-04-07T08:33:22.000+02:00
- Bump format_version to 3.5.0 (same track as integrations that ship kibana/alerting_rule_template) so built zips validate against current package-spec kibana layout. - Remove validation.yml SVR00002 exclusion; dashboard already satisfies the time-filter check. - README: note Kibana 9.2+ requirement for alert rule templates. Addresses review feedback on #18102 (alerting_rule_template zip validation warning; clarify alerting vs stack version). Made-with: Cursor
diff --git a/packages/chargeback/changelog.yml b/packages/chargeback/changelog.yml
@@ -1,7 +1,7 @@
 # newer versions go on top
 - version: 0.3.1
   changes:
-    - description: "Rename config and billing fields to chargeable-unit terminology (conf_chargeable_unit_rate, conf_chargeable_unit_rate_unit, total_chargeable_units). Fix billing_cluster_cost when ess.billing.deployment_tags is a string. Add dashboard @timestamp exists filter for package validation. Update dashboard ES|QL, ingest pipeline, and documentation. Bump transform pipeline and fleet_transform_version to 0.3.1. Dashboard ES|QL uses COALESCE so 0.3.0 lookup documents remain compatible after in-place upgrade."
+    - description: "Rename config and billing fields to chargeable-unit terminology (conf_chargeable_unit_rate, conf_chargeable_unit_rate_unit, total_chargeable_units). Fix billing_cluster_cost when ess.billing.deployment_tags is a string. Add dashboard @timestamp exists filter for package validation. Update dashboard ES|QL, ingest pipeline, and documentation. Bump transform pipeline and fleet_transform_version to 0.3.1. Dashboard ES|QL uses COALESCE so 0.3.0 lookup documents remain compatible after in-place upgrade. Bump package format_version to 3.5.0 so kibana/alerting_rule_template assets match package-spec; drop validation.yml SVR00002 override."
       type: enhancement
       link: https://github.com/elastic/integrations/pull/18102
 - version: 0.3.0
diff --git a/packages/chargeback/docs/README.md b/packages/chargeback/docs/README.md
@@ -50,7 +50,7 @@ POST chargeback_conf_lookup/_update/config
     "conf_query_weight": 20,
     "conf_storage_weight": 40,
     "conf_start_date": "2024-01-01T00:00:00.000Z",
-    "conf_end_date": "2024-12-31T23:59:59.999Z"
+    "conf_end_date": "2024-12-31T23:tie"
   }
 }
 ```
@@ -119,12 +119,6 @@ Chargeback data can be viewed in the `[Chargeback] Cost and Consumption breakdow
 
 ![Cost and Consumption breakdown](../img/chargeback.png)
 
-### Upgrading from 0.3.0
-
-From **0.3.1** onward, configuration and billing fields use chargeable-unit names (for example `conf_chargeable_unit_rate` and `total_chargeable_units` instead of `conf_ecu_rate` and `total_ecu`). The dashboard queries accept both the new and the previous field names, so you do not need to change existing documents in the lookup indices for panels to work. New data from the updated transforms uses the new names over time.
-
-If you built your own ES|QL, dashboards, or automation against the lookup indices, update those to the new field names when convenient.
-
 ## Deployment Groups
 
 The integration supports organizing deployments into logical groups using the `chargeback_group` tag on ESS Billing deployments. This enables cost allocation and filtering by teams, projects, or any organizational structure.
@@ -148,6 +142,8 @@ This integration includes 3 pre-configured alert rule templates that can be inst
 2. **New Chargeback Group Detected** - Notifies when a new `chargeback_group` tag is added to a deployment
 3. **Deployment with Chargeback Group Missing Usage Data** - Detects when a deployment has a chargeback group assigned but is not sending usage/consumption data
 
+The templates ship as Kibana alerting rule assets with the package and need **Kibana 9.2.0 or newer**, the same minimum as the integration’s Kibana version condition (see **Requirements** below).
+
 **Important:** For alert rules 2 and 3, ensure that the Chargeback transforms are running before setting them up. These alerting rules query the lookup indices created by the transforms (`billing_cluster_cost_lookup`, `cluster_deployment_contribution_lookup`, etc.). If the transforms are not started, the alerts will not function correctly.
 
 ### Alert actions
diff --git a/packages/chargeback/manifest.yml b/packages/chargeback/manifest.yml
@@ -1,4 +1,4 @@
-format_version: 3.4.0
+format_version: 3.5.0
 name: chargeback
 title: "Chargeback"
 version: 0.3.1
diff --git a/packages/chargeback/validation.yml b/packages/chargeback/validation.yml

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-format_version: 3.4.0`
	`1`	`+format_version: 3.5.0`
`2`	`2`	`name: chargeback`
`3`	`3`	`title: "Chargeback"`
`4`	`4`	`version: 0.3.1`