Skip to main content
Grafana is the metrics and log surface for your StarTree Cloud cluster. It is where you see a signal over time — the last hour, the last week, before and after a change — as opposed to the current-state views in the Data Portal. It reads only your own cluster’s data.

​
Getting there

1

Open it from the Data Portal

In the Data Portal left navigation, go to Monitoring → Grafana Dashboard. It opens in a new tab.
2

Sign in with the same identity provider

Grafana uses the same single sign-on as the Data Portal, so in most cases you land already authenticated. If you are prompted, sign in with the same credentials you use for StarTree Cloud.
Each cluster environment has its own Grafana. If you have more than one environment, there is no combined view across them, and a dashboard link from one environment will not resolve against another — always follow the link from the Data Portal you are working in.

​
Panels embedded in the Data Portal

You do not always have to leave the Data Portal. The task views embed Grafana panels directly, scoped to the work you are looking at: Embedded panels carry a Refresh and a Reconnect to Grafana action, and a time-range selector on the task-plan views. For anything beyond that — a wider window, a different query, a table-level view — go to the dashboards directly.
Embedded panels need a live Grafana session in the same browser. When one is not detected you will see a Sign in to Grafana prompt — click it, complete sign-in in the tab that opens, and return; the panels mount shortly afterwards. Panel embedding is enabled per environment, so on some environments the panels link out to Grafana rather than rendering inline.

​
Dashboard catalogue

Dashboards are organized into folders. Use the search icon or Dashboards in the Grafana navigation to list them.

​
Pinot

The core set. Most investigations start here.

​
Logging

Log search for your cluster’s components. Covered in detail in Accessing logs.

​
Capacity and resources

Other folders cover the infrastructure your environment runs on. They are useful for one specific question — confirming that a component was restarted or killed for memory rather than crashing on its own — and Troubleshooting resource pressure covers when that matters. Otherwise, start from the Pinot dashboards, which are the ones expressed in terms of tables, queries, and segments.

​
Reading the Pinot dashboards

Three things to do before drawing conclusions from a panel:
1

Set the template variables

Most Pinot dashboards have selectors at the top — table, server, partition, task type. A panel with no table selected is showing you either everything summed together or nothing. Table names carry their type suffix, so orders_REALTIME and orders_OFFLINE are separate entries for a hybrid table.
2

Widen the time range past the incident

The default range is short. Widen to at least several times the duration of what you are investigating — a latency step change is only visible if the window contains both sides of it. When comparing against an upgrade or config change, put the change roughly in the middle.
3

Check whether a flat line is zero or absent

A metric with no recorded value is absent rather than zero, so an empty panel can mean “this never happened” — a task type that has not run, a table never queried. Confirm against a related panel that you know should have data before treating emptiness as a finding.

​
Building your own charts

You have full access to query your cluster’s metrics, and creating dashboards is the normal way to track something specific to your workload.
1

Start from a panel that nearly works

Open the panel menu on any built-in panel and choose Explore. You get its query with the correct metric name, labels, and aggregation already in place — far quicker and less error-prone than composing one from scratch.
2

Adjust the query

See the metrics reference for the naming convention, the available suffixes, and the label set. The most common mistake is aggregating across the wrong label — check what labels the series actually carries before adding a sum by.
3

Save into your own folder

Create a new dashboard rather than editing a built-in one, and save it in a folder of your own.
Do not edit the built-in dashboards. StarTree maintains them, so an edit you make in place can be replaced without warning when they are updated. Duplicate the dashboard instead (Dashboard settings → Save as), put the copy in your own folder, and edit that.

​
Retention and limits

Metrics and logs are retained for a bounded window — long enough for post-incident analysis, not long enough for capacity planning across quarters. If you need a trend over a longer period than Grafana holds, export the panel data (Panel → Inspect → Data) while it is still in range, or ask your StarTree team what the retention is for your environment. For log retention specifically, see Accessing logs.

​
If you cannot get in