---
title: Service explorer | Tiger Data Docs
description: Monitor service health and performance with the Service Explorer dashboard
---

Service explorer in Tiger Console provides a rich administrative dashboard for understanding the state of your database instance. The explorer gives you insight into the performance of your database, giving you greater confidence and control over your data.

The explorer works like an operations center as you develop and run your applications with Tiger Cloud. It gives you quick access to the key properties of your database, like table sizes, schema definitions, and foreign key references, as well as information specific to Tiger Cloud, like information on your hypertables and continuous aggregates.

To see the explorer, select your service in Console and click `Explorer`.

## General information

In the `General information` section, you can see a high-level summary of your service. This includes:

- all your hypertables, relational tables, and continuous aggregates.
- overall compression ratios with original and compressed sizes. Hover over `On-disk size` to split it into the columnstore and rowstore amounts. `Rowstore` here covers hypertable and continuous aggregate data still in regular row format, including its indexes; plain PostgreSQL tables are not counted.
- other policy and continuous aggregate data.

![Service explorer](/docs/_astro/tiger-console-service-explorer.BYvPS9HG_2bszjt.webp) ![Service explorer](/docs/_astro/tiger-console-service-explorer-dark.CcTKBa36_ZELeWn.webp)

## Tables

You can have a detailed look into all your tables, including information about table schemas, table indexes, and foreign keys. For your hypertables, it shows details about chunks, continuous aggregates, and policies such as data retention policies and data reordering. You can also inspect individual hypertables, including their sizes, dimension ranges, and columnstore compression status.

From this section, you can also set an automated policy to compress chunks into the columnstore. For more information, see the [hypercore documentation](/docs/learn/columnar-storage/understand-hypercore/index.md).

When you inspect a hypertable, a timeline chart visualizes its chunks, showing their relative sizes and whether each is in the rowstore or the columnstore. By default, the chart shows the latest 100 chunks; click and drag to zoom in on a specific time range. The chart also shows the status of the latest runs for the hypertable's columnstore job, with a link to the job's deep dive page.

![Service explorer tables](/docs/_astro/tiger-console-columstore-data-savings.D2y47SR-_ZwFrrA.webp) ![Service explorer tables](/docs/_astro/tiger-console-columstore-data-savings-dark.BV7QYIpN_Z1jgSmM.webp)

For more information about hypertables, see the [hypertables section](/docs/learn/hypertables/understand-hypertables/index.md).

## Columnstore

In the `Columnstore` section, you see every hypertable and continuous aggregate alongside how its data is stored right now:

- `Size`: the whole object on disk, indexes and TOAST included.
- `Rowstore`: the part of that size still in regular row format.
- `Columnstore`: the part converted to the compressed columnar format. Objects with no columnstore data show `-`.
- `Compression`: how much space the conversion saves, in percent. Objects you have not converted yet show `Convert to columnstore` instead, which opens the conversion wizard.

Sort by `Size`, `Rowstore`, or `Columnstore` to find the objects that gain the most from the columnstore.

## Continuous aggregates

In the `Continuous aggregate` section, you can see all your continuous aggregates, including top-level information such as their size, whether they are configured for real-time aggregation, and their refresh periods.

![Service explorer caggs](/docs/_astro/tiger-console-service-explorer-caggs.k3bx2CEi_1wSBTK.webp) ![Service explorer caggs](/docs/_astro/tiger-console-service-explorer-caggs-dark.C4UWADpg_2aEdCd.webp)

For more information about continuous aggregates, see the [continuous aggregates section](/docs/build/continuous-aggregates/create-a-continuous-aggregate/index.md).