> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/products/database/how-tos/monitor-a-database.md).
# Monitor a database
***
At the very bottom of the overview page of your database, you find the address for the monitoring page. Note that this page is also affected by the firewall, hence it can only be reached from the IP addresses that you've allowed. See [Manage access](/products/database/how-tos/manage-access.md) on how to add IP addresses that are allowed to connect.
The metrics provided by the URL in the **Monitoring** section of the overview page are in a format called *Prometheus metric exposition*. This format can be ingested by tools such as InfluxDB scrapers and Prometheus itself.
Below is a short snippet of the metric data:
{% code title="Example metric" %}
```
# HELP disk_free Telegraf collected metric
# TYPE disk_free gauge
disk_free{device="sda2",fstype="ext4",host="db-4f959",label="",mode="rw",path="/"} 2.5386483712e+10
disk_free{device="tmpfs",fstype="tmpfs",host="db-4f959",label="",mode="rw",path="/dev/shm"} 2.044461056e+09
disk_free{device="tmpfs",fstype="tmpfs",host="db-4f959",label="",mode="rw",path="/run"} 4.078592e+08
disk_free{device="tmpfs",fstype="tmpfs",host="db-4f959",label="",mode="rw",path="/run/lock"} 5.24288e+06
disk_free{device="udev",fstype="devtmpfs",host="db-4f959",label="",mode="rw",path="/dev"} 2.006528e+09
```
{% endcode %}
## Ingesting the database metrics into InfluxDB
To start ingesting metrics into InfluxDB, begin by creating a new bucket. Inside InfluxDB, hover over the up-arrow icon and click **Buckets**.
Now, click **Create bucket**.
In the dialog box that appears, enter a name for the bucket. In this example, we’ll name it *glesys-my-test-db*. Then, click **Create**.
Next, click the **Scrapers** tab, then **Create scraper**.
You need to provide some information for your scraper. In this example, we name the scraper *Glesys scraper my-test-db*. You also need to select where the scraper should store the data—here, choose the bucket you created earlier.
In the **Target URL** field, enter the URL for the metrics. This URL can be found under the **Monitoring** section on the overview page of your database.
Everything is now set up and ready. To explore the metrics, click the graph icon to open **Data Explorer**.
To make things easier, toggle **Switch to old Data Explorer**. From here, you can click through the available metrics to visualize them.
First, select the bucket with the data; in this example, it's *glesys-my-test-db*. Then, choose the metrics *disk\_total* and *disk\_used*. In the **Field** column, select *gauge*. In the next column, switch to **path** and select the root path indicated by a forward slash. Finally, click **Submit**.
You can now hover over the graph to see exactly how much storage your database has and how much you've used.
---
# 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.glesys.com/products/database/how-tos/monitor-a-database.md?ask=&goal=
```
`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.