Add version 0.2.8 with alerting rule templates and auto-start transforms

- Add three Kibana alerting rule templates:
  * Transform Health Monitoring
  * New Chargeback Group Detection
  * Missing Usage Data
- Enable auto-start for all transforms (eliminates manual startup)
- Update documentation to reflect auto-start behavior
- Add Alerting Rules section to README
- Update Instructions with alerting configuration steps

Related to elastic/integrations#16229

Author: JohannesMahne

integration/Instructions.md

@@ -36,7 +36,7 @@ PUT chargeback_conf_lookup
   "mappings": {
     "_meta": {
       "managed": true,
-      "package": { "name": "chargeback", "version": "0.2.7" }
+      "package": { "name": "chargeback", "version": "0.2.8" }
     },
     "properties": {
       "config_join_key": { "type": "keyword" },
@@ -126,7 +126,7 @@ POST chargeback_conf_lookup/_doc
 
 ### 3. Upload ZIP File: 
 
-- Asset: [`chargeback-0.2.7.zip`](assets/0.2.7/chargeback-0.2.7.zip)
+- Asset: [`chargeback-0.2.8.zip`](assets/0.2.8/chargeback-0.2.8.zip)
 - Browse to Integrations, and click on `+ Create new integration`
 
 ![alt text](assets/img/CreateNewIntegration.png)
@@ -135,10 +135,22 @@ POST chargeback_conf_lookup/_doc
 
 ![alt text](assets/img/UploadItAsAZip.png)
 
+### 4. Transforms Auto-Start
+
+Starting from version 0.2.8, all Chargeback transforms are configured to auto-start upon installation. You no longer need to manually start the transforms.
+
+### 5. Configure Alerting Rules (Optional)
+
+Version 0.2.8 includes three pre-configured alerting rule templates:
+- **Transform Health Monitoring** - Monitors transform health status
+- **New Chargeback Group Detection** - Alerts on new chargeback group tags
+- **Missing Usage Data** - Detects deployments with missing usage data
+
+These rules can be configured in **Stack Management → Rules** after installation.
 
 ## Upgrade integration
 
 To upgrade the integration, do the following:
 - Depending on the change in version, you might need to delete the `*_lookup` indices, and create them again.
 - Upload the new asset (ZIP) file to Kibana.
-- Start the transforms.
+- For versions prior to 0.2.8, start the transforms manually. From 0.2.8 onwards, transforms auto-start.

integration/README.md

@@ -2,7 +2,7 @@
 
 ## Version
 
-Chargeback integration: 0.2.7
+Chargeback integration: 0.2.8
 
 ## Dependencies
 
@@ -47,7 +47,7 @@ The first layer of processing that we do, is five transforms:
 
 ![Transforms](assets/img/Transforms.png)
 
-All of the transforms create their own lookup index. There is also a lookup index for the configuration. The usage transforms need to be started manually.
+All of the transforms create their own lookup index. There is also a lookup index for the configuration. Starting from version 0.2.8, all transforms are configured to auto-start upon installation.
 
 ![Lookup Indices](assets/img/LookupIndices.png)
 
@@ -67,4 +67,14 @@ Once you have uploaded the integration, you can navigate to the `[Chargeback] Co
 
 ## Sample dashboard
 
-![Chargeback](<assets/img/[Chargeback] Cost and Consumption breakdown.png>)
+![Chargeback](<assets/img/[Chargeback] Cost and Consumption breakdown.png>)
+
+## Alerting Rules
+
+Version 0.2.8 includes three pre-configured Kibana alerting rule templates to help monitor your Chargeback integration:
+
+1. **Transform Health Monitoring** - Monitors the health status of all Chargeback transforms and alerts when issues are detected
+2. **New Chargeback Group Detection** - Notifies when a new `chargeback_group` tag is added to a deployment
+3. **Missing Usage Data** - Alerts when a deployment with a chargeback group assigned is not sending usage/consumption data
+
+These alerting templates are automatically installed with the integration and can be configured through **Stack Management → Rules** in Kibana.

integration/assets/0.2.8/chargeback-0.2.8.zip

@@ -0,0 +1,54 @@
+# Create the config lookup index for chargeback configuration.
+# This index will store configuration settings. Multiple documents can be added for different time periods.
+
+PUT chargeback_conf_lookup
+{
+  "settings": { 
+    "index.mode": "lookup", 
+    "index.hidden": true 
+  },
+  "mappings": {
+    "_meta": {
+      "managed": true,
+      "package": { "name": "chargeback", "version": "0.2.8" }
+    },
+    "properties": {
+      "config_join_key": { "type": "keyword" },
+      "conf_ecu_rate": { "type": "float" },
+      "conf_ecu_rate_unit": { "type": "keyword"},
+      "conf_indexing_weight": { "type": "integer" },
+      "conf_query_weight": { "type": "integer" },
+      "conf_storage_weight": { "type": "integer" },
+      "conf_start_date": {"type": "date"},
+      "conf_end_date": {"type": "date"}
+    }
+  }
+}
+
+# Add the default configuration to the chargeback_conf_lookup index with ID "config".
+# This creates a document that can be updated later using _update/config.
+POST chargeback_conf_lookup/_doc/config
+{
+  "config_join_key": "chargeback_config",
+  "conf_ecu_rate": 0.85,
+  "conf_ecu_rate_unit": "EUR",
+  "conf_indexing_weight": 20,
+  "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"
+}
+
+# Add additional configuration for a different time period (optional).
+# This creates a new document with an auto-generated ID for time-based rate changes.
+POST chargeback_conf_lookup/_doc
+{
+  "config_join_key": "chargeback_config",
+  "conf_ecu_rate": 0.95,
+  "conf_ecu_rate_unit": "EUR",
+  "conf_indexing_weight": 20,
+  "conf_query_weight": 20,
+  "conf_storage_weight": 40,
+  "conf_start_date": "2025-01-01T00:00:00.000Z",
+  "conf_end_date": "2025-12-31T23:59:59.999Z"
+}