# Querying Data

### Primary Methods

#### Data Explorer (UI Mode)

The **Data Explorer** offers a visual interface for building queries without writing code.

It supports multiple data sources and lets you query your metrics using either the **MetricsQL Builder** or the **groundcover Query Language Builder**.

**Learn More:** [**Explore & Monitors Query Builder**](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/querying-your-groundcover-data/explore-and-monitors-query-builder.md)

You can switch between UI Mode and Code Mode at any time in the Explore and Monitors sections.

#### Native Pages (Logs/Traces/Events)

groundcover’s native pages use the same filtering syntax as the Data Explorer and Code Mode. Learn more [here](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/querying-your-groundcover-data/groundcover-query-language/filters.md).

#### API

[groundcover’s API](broken://pages/Cw1sNLGEwmaSTxQXhV8R) uses the same query interface as the Data Explorer.\
It supports both **groundcover Query Language** and **MetricsQL** queries.

#### Logs/Traces/Events Query Bar Code Mode

The **Query Bar**, used across the Data Explorer, Dashboards, and Monitor Wizard, lets users switch between **Builder** and **Code** modes.

For **Logs/Traces/Events** it uses the **groundcover Query Language**,  designed for full control over your data.

**It's perfect for:**

* Complex filtering with boolean logic
* Statistical aggregations and percentiles
* Joining data across multiple queries
* Advanced transformations and formatting
* Building precise monitors and dashboards

**Get Started:**

* [**Query Language Overview**](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/querying-your-groundcover-data/groundcover-query-language.md) - Introduction and quick start
* [**Filters**](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/querying-your-groundcover-data/groundcover-query-language/filters.md) - Field matching, wildcards, boolean logic
* [**Aggregations**](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/querying-your-groundcover-data/groundcover-query-language/aggregations.md) - Statistical functions and grouping
* [**Join Operations**](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/querying-your-groundcover-data/groundcover-query-language/join-operations.md) - Combine multiple queries
* [**Pipeline Operations**](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/querying-your-groundcover-data/groundcover-query-language/pipeline-operations.md) - Sort, limit, fields, and more

**Quick Example:**

```
level:error namespace:production | stats by (workload) count() errors | sort by (errors desc) | limit 10
```

*Top 10 workloads with errors in production*

***

### Legacy Methods (Grafana)

groundcover includes embedded Grafana for users who prefer Grafana's query interfaces. These methods are still fully supported.

#### Query via Grafana

* [**Query your logs**](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/querying-your-groundcover-data/querying-data-with-grafana-legacy/query-your-logs.md) - Grafana-based log querying
* [**Query your metrics**](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/querying-your-groundcover-data/querying-data-with-grafana-legacy/query-your-metrics.md) - PromQL in Grafana
* [**Using KEDA autoscaler with groundcover**](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/querying-your-groundcover-data/querying-data-with-grafana-legacy/using-keda-autoscaler-with-groundcover.md) - Advanced use case


---

# Agent Instructions: 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:

```
GET https://docs.groundcover.com/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/querying-your-groundcover-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.