From 916a135e963d89e1da042eab577952c04ce6434e Mon Sep 17 00:00:00 2001 From: jakubgalecki0 Date: Wed, 6 May 2026 12:46:51 +0200 Subject: [PATCH 1/2] [azure_billing] enable agentless deployment --- packages/azure_billing/_dev/build/docs/README.md | 14 ++++++++++++++ packages/azure_billing/changelog.yml | 5 +++++ packages/azure_billing/docs/README.md | 14 ++++++++++++++ packages/azure_billing/manifest.yml | 12 ++++++++++-- 4 files changed, 43 insertions(+), 2 deletions(-) diff --git a/packages/azure_billing/_dev/build/docs/README.md b/packages/azure_billing/_dev/build/docs/README.md index a7964748e6c..5d4c7311d8d 100644 --- a/packages/azure_billing/_dev/build/docs/README.md +++ b/packages/azure_billing/_dev/build/docs/README.md @@ -6,6 +6,20 @@ The integration uses the [Azure Consumption API](https://docs.microsoft.com/en-u Use the Azure Billing Metrics integration to collect detailed resource usage and forecast expenses for the coming weeks. For example, if you want to know which resources cost you most, you could view the top resources donut chart included in the dashboard for this integration. Then you can visualize the prediction for the coming weeks by looking at the forecast chart. +## How do I deploy this integration? + +### Agent-based deployment + +Elastic Agent must be installed. For more details, check the Elastic Agent [installation instructions](https://www.elastic.co/docs/reference/fleet/install-elastic-agents). You can install only one Elastic Agent per host. + +Elastic Agent is required to collect data from Azure and ship the data to Elastic, where the events will then be processed via the integration's ingest pipelines. + +### Agentless deployment + +Agentless integrations allow you to collect data without having to manage Elastic Agent in your cloud. They make manual agent deployment unnecessary, so you can focus on your data instead of the agent that collects it. For more information, refer to [Agentless integrations](https://www.elastic.co/guide/en/serverless/current/security-agentless-integrations.html) + +Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. This functionality is in beta and is subject to change. Beta features are not subject to the support SLA of official GA features. + ## Data streams diff --git a/packages/azure_billing/changelog.yml b/packages/azure_billing/changelog.yml index 91b4a75611c..0e959a7f59f 100644 --- a/packages/azure_billing/changelog.yml +++ b/packages/azure_billing/changelog.yml @@ -1,3 +1,8 @@ +- version: "1.10.0" + changes: + - description: Add support for agentless deployment. + type: enhancement + link: https://github.com/elastic/integrations/pull/18391 - version: "1.9.0" changes: - description: Add a flag `fips_compatible` to control whether the package is allowed in the ECH FedRAMP High environment. diff --git a/packages/azure_billing/docs/README.md b/packages/azure_billing/docs/README.md index 41e2651a65c..8a0025709e4 100644 --- a/packages/azure_billing/docs/README.md +++ b/packages/azure_billing/docs/README.md @@ -6,6 +6,20 @@ The integration uses the [Azure Consumption API](https://docs.microsoft.com/en-u Use the Azure Billing Metrics integration to collect detailed resource usage and forecast expenses for the coming weeks. For example, if you want to know which resources cost you most, you could view the top resources donut chart included in the dashboard for this integration. Then you can visualize the prediction for the coming weeks by looking at the forecast chart. +## How do I deploy this integration? + +### Agent-based deployment + +Elastic Agent must be installed. For more details, check the Elastic Agent [installation instructions](https://www.elastic.co/docs/reference/fleet/install-elastic-agents). You can install only one Elastic Agent per host. + +Elastic Agent is required to collect data from Azure and ship the data to Elastic, where the events will then be processed via the integration's ingest pipelines. + +### Agentless deployment + +Agentless integrations allow you to collect data without having to manage Elastic Agent in your cloud. They make manual agent deployment unnecessary, so you can focus on your data instead of the agent that collects it. For more information, refer to [Agentless integrations](https://www.elastic.co/guide/en/serverless/current/security-agentless-integrations.html) + +Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. This functionality is in beta and is subject to change. Beta features are not subject to the support SLA of official GA features. + ## Data streams diff --git a/packages/azure_billing/manifest.yml b/packages/azure_billing/manifest.yml index 9d797b16d8b..bef39710f60 100644 --- a/packages/azure_billing/manifest.yml +++ b/packages/azure_billing/manifest.yml @@ -1,6 +1,6 @@ name: azure_billing title: Azure Billing Metrics -version: "1.9.0" +version: "1.10.0" description: Collect billing metrics with Elastic Agent. type: integration icons: @@ -13,7 +13,7 @@ screenshots: title: App State Overview size: 5120x2562 type: image/png -format_version: "3.0.2" +format_version: "3.3.2" categories: - cloud - observability @@ -79,6 +79,14 @@ policy_templates: title: Azure Billing Metrics description: Collect billing information with Elastic Agent. fips_compatible: false + deployment_modes: + default: + enabled: true + agentless: + enabled: true + organization: observability + division: engineering + team: obs-infraobs-integrations data_streams: - billing inputs: From 8b536f4f0f7d06f79de9d0fe6268f42fc07da67d Mon Sep 17 00:00:00 2001 From: jakubgalecki0 Date: Wed, 6 May 2026 12:49:11 +0200 Subject: [PATCH 2/2] add pr link --- packages/azure_billing/changelog.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/azure_billing/changelog.yml b/packages/azure_billing/changelog.yml index 0e959a7f59f..957f8f02a62 100644 --- a/packages/azure_billing/changelog.yml +++ b/packages/azure_billing/changelog.yml @@ -2,7 +2,7 @@ changes: - description: Add support for agentless deployment. type: enhancement - link: https://github.com/elastic/integrations/pull/18391 + link: https://github.com/elastic/integrations/pull/18848 - version: "1.9.0" changes: - description: Add a flag `fips_compatible` to control whether the package is allowed in the ECH FedRAMP High environment.