> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/metrics-and-definitions/quality/hotfix-rate.md).

# Hotfix Rate

Hotfix Rate is defined as the percentage of changes to a production or live environment to fix any degraded service. In other words, hotfixes to address production bugs.

<div data-with-frame="true"><figure><img src="/files/44Vfn3XRInojX32zdzwJ" alt="" width="563"><figcaption></figcaption></figure></div>

The way Hivel identifies the PRs to be considered for CFR is through the configurations - through pull request patterns, JIRA issue types, or by patch version pattern.

<div data-with-frame="true"><figure><img src="/files/yhoINTAkXifZAbeYiP5m" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
Please note: **the PRs considered for Hotfix Rate are a subset of the total PRs deployed to release branches.**
{% endhint %}

Know more about how to setup the configurations [<mark style="color:purple;">here</mark>](https://hivel.gitbook.io/knowlegebase/setup/configurations-explained/hotfix-configurations).

#### Industry Benchmarking

<div data-with-frame="true"><figure><img src="/files/1n3fG8kCwTmVR1nMngw3" alt="" width="563"><figcaption></figcaption></figure></div>

#### Related article

{% content-ref url="/pages/Gum2b6JWkQTrUZsf6xrf" %}
[How to identify root cases of high change failure rates?](/improve-performance/how-to-improve-quality/how-to-identify-root-cases-of-high-change-failure-rates.md)
{% endcontent-ref %}

{% content-ref url="/pages/qvT5Y70xU01sAD0knK62" %}
[Building a feedback loop for continuous code improvement](/improve-performance/how-to-improve-quality/building-a-feedback-loop-for-continuous-code-improvement.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hivel.ai/metrics-and-definitions/quality/hotfix-rate.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.