> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/dashboards/adding-widgets/chart-widget/line-chart.md).

# Line Chart

Configure a Kilo Line chart for a metric's history, with threshold bands, an average, and the current value.

A Line chart is one of the two presentations inside the **Chart** widget. It connects consecutive readings into a continuous trace, making gradual movement, drift, cycles, and sudden spikes easy to see.

Use Line for temperature, pressure, energy demand, humidity, and other measurements where the shape of the trend matters more than comparing individual reports.

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-60d8820649747df0c38f65f0bc0a985c7e08ece7%2Fchart-widget-line.jpg?alt=media" alt="Kilo Chart appearance settings with Line selected and a line preview with threshold bands"><figcaption></figcaption></figure>

## Configure the Line type

1. Open a dashboard in edit mode and select **Chart** from the widget picker.
2. On **Datasource**, add one device and one numeric metric.
3. Click **Next** and set **Widget type** to **line**.
4. Choose the **Timeframe**: Last hour, Last day, Last week, or Last month, subject to the data retention included in the plan.
5. Set the vertical **Value range** with **From** and **To**.
6. Add any threshold bands, average line, axis lines, and legend needed by operators.
7. Turn on **Show metrics below** when the metric name and current reading should remain visible beneath the plot.
8. Click **Save**.

The **Display value on bar** setting does not appear for Line because there are no bars to label.

## Read the result

The large value shows the latest reading. The line shows how that metric moved over the selected period. If the current reading falls inside a configured threshold, the large value adopts that threshold's color; the line keeps the metric color selected on Datasource.

For a server-room temperature chart, a week-long line makes an overnight cooling failure visible as a rise out of the normal band and shows when the reading returned to baseline.

## See also

* [Chart Widget](/dashboards/adding-widgets/chart-widget.md) — shared Chart data and appearance settings
* [Bar Chart](/dashboards/adding-widgets/chart-widget/bar-chart.md) — compare individual reports instead
* [Last Data Widget](/dashboards/adding-widgets/last-data-widget.md) — show only the latest state


---

# 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.kiloiot.io/dashboards/adding-widgets/chart-widget/line-chart.md?ask=<question>&goal=<user_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.
