> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/resilience-testing/shared-capabilities/license-consumption.md).

# License Consumption

Harness CE services license consumption

Harness Chaos Engineering module uses 'Services' as a key construct in identifying the target resources for chaos experimentation. Harness Chaos Engineering customers license by Developers (Developer 360 model) and receive services as an included entitlement. Licenses are measured over a yearly cycle. Go to [Subscriptions and licenses](https://developer.harness.io/harness-platform/subscriptions-and-licenses/subscriptions) for more details about the Developer 360 model.

## What is a service? <a href="#what-is-a-service" id="what-is-a-service"></a>

In the Harness Chaos Engineering module, a **Service** refers to the specific target resource undergoing chaos experiments. This could include a variety of resources such as Kubernetes clusters, VMware instances, Windows or Linux servers, PCF applications, and popular cloud platforms.

The table below describes how a **Service** is considered in Chaos Engineering, in the context of the target resource.

| Target Resource                                                 | Chaos Service Mapping                                                                                                                                                                                                | Target Resource : Chaos Service License |
| --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- |
| Kubernetes Platform                                             | One license service is equivalent to a Kubernetes service or a workload such as a Deployment/ReplicaSet/StatefulSet/DaemonSet/Job/CronJob.                                                                           | 1:1                                     |
| Virtual Machine or a Baremetal host running Windows or Linux OS | The virtual machine can be a VMware VM, a hypervisor VM, or any cloud provider VM such as EC2, GCP VM, or Azure VM. This has a one-to-one mapping with the license service.                                          | 1:1                                     |
| Serverless functions                                            | Cloud providers offer serverless functions such as AWS Lambda, GCP Cloud Functions, or Azure Functions. Chaos experiments on 5 serverless functions are mapped to a license service.                                 | 5:1                                     |
| Cloud Resources and Container Services                          | This could be AWS Load Balancers for AZ failures, AWS ECS, Azure Container Apps, or GCP Cloud Run. This has a one-to-one mapping with the license service.                                                           | 1:1                                     |
| Miscellaneous (experiment runs)                                 | Any target resource that does not fall into a specific type described above, will fall in the miscellaneous category. In this category, 100 chaos experiment runs on a given target are mapped to a license service. | 100:1                                   |

## Service license count <a href="#service-license-count" id="service-license-count"></a>

For a Resilience Testing subscription, the Subscriptions page shows three views of service license usage. They do not measure the same thing.

| View                   | What it shows                                                                                                                                                                                                                   |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Usage Overview**     | The service licenses used in the current license period, against the number purchased, and the remaining balance. The current license period is the year that starts on your license start date.                                |
| **Usage Details**      | The same count broken down by service type for the selected period, which defaults to the current license period. The information icon on each service type shows the ratio of targets to one license service for your account. |
| **Utilization Growth** | Usage over time, as a cumulative chart.                                                                                                                                                                                         |

The number in **Usage Overview** is your licensed count. **Utilization Growth** shows a trend over time and is not the licensed count, so it can differ from **Usage Overview**.

A service is counted once in a period if at least one chaos experiment ran against it in that period. Harness identifies a unique service by the service identifier together with the Resilience Testing infrastructure that ran the experiment. The same service identifier tested from two infrastructures, for example from two projects or two clusters, counts as two services. This is why the **Utilization Details** export can list the same service identifier on more than one row.

Have questions? Go to [Frequently Asked Questions on Licenses](https://developer.harness.io/faqs/chaos-engineering-faqs.md#license).

<details>

<summary>How is Resilience Testing priced?</summary>

Customers license by Developers under the Developer 360 model and receive Services as an included entitlement. Licenses are measured over a yearly cycle. A Kubernetes workload, a virtual machine, or a cloud resource maps 1:1 to a license service. Five serverless functions map to one license service. One hundred miscellaneous experiment runs on a target map to one license service. This page does not publish a price list. Go to [Subscriptions and licenses](https://developer.harness.io/harness-platform/subscriptions-and-licenses/subscriptions) for the Developer 360 model.

</details>

## Troubleshooting <a href="#troubleshooting" id="troubleshooting"></a>

<details>

<summary>The license services consumed do not match the number of chaos targets</summary>

A target does not always map to one license service. Kubernetes workloads, virtual machines, and cloud resources map 1:1, five serverless functions map to one license service, and a miscellaneous target consumes one license service for every 100 chaos experiment runs. Go to [Frequently Asked Questions on Licenses](https://developer.harness.io/faqs/chaos-engineering-faqs.md#license) to review other license questions.

</details>

{% @harness-feedback/feedback %}
