> For the complete documentation index, see [llms.txt](https://docs.vitaracharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vitaracharts.com/readme/gradient-threshold.md).
# Gradient Threshold
A new threshold condition called ‘Gradient threshold’ is added to the following charts in the threshold’s properties: Bar, Stacked Bar, Column, Stacked Column, Line, Area, Bubble, Tornado, Sparkline, Heatmap, Column range, Bullet, Calendar Heatmap, Trellis, Mekko, Word Cloud, Dumbbell, Slope, Angular Gauge, and Sankey chart.
Gradient thresholds with the required number of stops are applied between two colors. Gradient thresholds are applied to Attributes and Metrics with the Start and End colors based on the Target and Source settings.
Click on the Edit Button→ Thresholds Button→ We can set Gradient Thresholds through conditions.
Examples for Gradient Threshold:
1. In the below screenshot, for the Angular Gauge Chart, we applied the Gradient threshold on Background Bar, and Red as Start color and Yellow as End color, with 5 Stops.
2. In the below screenshot, in the Dumbbell chart, we applied Target and Source as Cost, and applied Gradient threshold condition, with alias name and number of stops at 4.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.vitaracharts.com/readme/gradient-threshold.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
